Skip to content
No description, website, or topics provided.
C++ C Python M4 Makefile HTML Other
Branch: master
Clone or download
Platincoin Master
2
Latest commit 9f1c57c Jun 21, 2018
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.tx Platincoin Release 2018.14.110.2 Jun 21, 2018
build-aux/m4 Platincoin Release 2018.14.110.2 Jun 21, 2018
contrib Platincoin Release 2018.14.110.2 Jun 21, 2018
debian Platincoin Release 2018.14.110.2 Jun 21, 2018
depends Platincoin Release 2018.14.110.2 Jun 21, 2018
doc Platincoin Release 2018.14.110.2 Jun 21, 2018
qa Platincoin Release 2018.14.110.2 Jun 21, 2018
share Platincoin Release 2018.14.110.2 Jun 21, 2018
src Platincoin Release 2018.14.110.8 Jun 21, 2018
tools Platincoin Release 2018.14.110.2 Jun 21, 2018
.gitattributes Platincoin Release 2018.14.110.2 Jun 21, 2018
.gitignore Platincoin Release 2018.14.110.2 Jun 21, 2018
.gitlab-ci.yml
.travis.yml Platincoin Release 2018.14.110.2 Jun 21, 2018
CONTRIBUTING.md Platincoin Release 2018.14.110.2 Jun 21, 2018
COPYING Platincoin Release 2018.14.110.2 Jun 21, 2018
INSTALL.md Platincoin Release 2018.14.110.2 Jun 21, 2018
Makefile.am Platincoin Release 2018.14.110.2 Jun 21, 2018
README.md Platincoin Release 2018.14.110.3 Jun 21, 2018
autogen.sh Platincoin Release 2018.14.110.2 Jun 21, 2018
config.orig.pri
configure.ac Platincoin Release 2018.14.110.8 Jun 21, 2018
libbitcoinconsensus.pc.in Platincoin Release 2018.14.110.2 Jun 21, 2018
plc-qt.pro Platincoin Release 2018.14.110.8 Jun 21, 2018

README.md

Platincoin Core integration/staging tree

License

Platincoin Core is released under the terms of the MIT license. See COPYING for more information or see https://opensource.org/licenses/MIT.

Development Process

The master branch is regularly built and tested, but is not guaranteed to be completely stable. Tags are created regularly to indicate new official, stable release versions of Platincoin Core.

The contribution workflow is described in CONTRIBUTING.md.

Testing

Testing and code review is the bottleneck for development; we get more pull requests than we can review and test on short notice. Please be patient and help out by testing other people's pull requests, and remember this is a security-critical project where any mistake might cost people lots of money.

Automated Testing

Developers are strongly encouraged to write unit tests for new code, and to submit new unit tests for old code. Unit tests can be compiled and run (assuming they weren't disabled in configure) with: make check. Further details on running and extending unit tests can be found in /src/test/README.md.

There are also regression and integration tests of the RPC interface, written in Python, that are run automatically on the build server. These tests can be run (if the test dependencies are installed) with: qa/pull-tester/rpc-tests.py

The Travis CI system makes sure that every pull request is built for Windows, Linux, and OS X, and that unit/sanity tests are run automatically.

Manual Quality Assurance (QA) Testing

Changes should be tested by somebody other than the developer who wrote the code. This is especially important for large or high-risk changes. It is useful to add a test plan to the pull request description if testing the changes is not straightforward.

You can’t perform that action at this time.