Skip to content

DriveNetTESTDRIVE/DriveNet

Folders and files

NameName
Last commit message
Last commit date

Latest commit

6667296 · Sep 13, 2019
Nov 16, 2017
Jan 24, 2018
Jun 28, 2018
Mar 22, 2019
Dec 22, 2017
Jun 28, 2018
Aug 3, 2018
Sep 13, 2019
Jun 28, 2018
Oct 29, 2014
Jun 28, 2018
Jun 29, 2018
Nov 20, 2017
Dec 31, 2017
Aug 5, 2018
Oct 5, 2016
Jun 28, 2018
Dec 25, 2018
Sep 21, 2016
Sep 13, 2019
Jun 28, 2018

Repository files navigation

DriveNet

Learn more about Drivechains here: http://drivechain.info

Start helping here: https://github.com/drivechain-project/bitcoin/issues

For an example sidechain implementation, see: https://github.com/drivechain-project/bitcoin/tree/sidechainBMM

What is DriveNet?

TODO

License

Bitcoin Core (and DriveNet) are 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 Bitcoin Core.

The contribution workflow is described in CONTRIBUTING.md.

The developer mailing list should be used to discuss complicated or controversial changes before working on a patch set.

Developer IRC can be found on Freenode at #bitcoin-core-dev.

Testing

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, written in Python, that are run automatically on the build server. These tests can be run (if the test dependencies are installed) with: test/functional/test_runner.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.