Go to file
Wladimir J. van der Laan 5242bb32c7
Merge pull request #6813
d80e3cb Support gathering of code coverage data for RPC tests (dexX7)
e3b5e6c Run extended BitcoinJ tests for coverage based on config (dexX7)
45d4ff0 Add config option to enable extended RPC tests for code coverage (dexX7)
8e3a27b Require Python for RPC tests, when using lcov (dexX7)
d425877 Remove coverage and test related files, when cleaning up (dexX7)
4d2a926 Ignore coverage data related and temporary test files (dexX7)
2015-10-26 09:09:33 +01:00
.tx Change transifex slug to translation-011x 2015-05-01 14:25:02 +02:00
build-aux/m4 build: make sure pkg-config checks are guarded by an m4_ifdef 2015-07-31 23:21:34 -04:00
contrib Merge pull request #6790 2015-10-23 10:45:50 +02:00
depends Merge pull request #6801 2015-10-20 12:35:54 +02:00
doc Merge pull request #6878 2015-10-26 08:21:03 +01:00
qa Merge pull request #6351 2015-10-23 13:33:13 +02:00
share [trivial] Remove obsolete share/qt/make_windows_icon.sh 2015-10-09 16:57:28 +02:00
src Remove coverage and test related files, when cleaning up 2015-10-23 22:09:14 +02:00
.gitattributes Separate protocol versioning from clientversion 2014-10-29 00:24:40 -04:00
.gitignore Merge pull request #6813 2015-10-26 09:09:33 +01:00
.travis.yml Migrated rpc-tests.sh to all python rpc-tests.py 2015-10-01 11:28:11 -07:00
autogen.sh Bugfix: Replace bashisms with standard sh to fix build on non-BASH systems 2014-10-03 23:45:26 +00:00
configure.ac Add config option to enable extended RPC tests for code coverage 2015-10-23 22:09:19 +02:00
CONTRIBUTING.md Add PR title prefix for trivial changes [skip ci] 2015-09-30 08:44:51 +02:00
COPYING Update contrib/debian/copyright 2015-09-15 16:38:08 +02:00
INSTALL Prettify some /Contrib READMEs 2013-10-21 20:07:31 -04:00
libbitcoinconsensus.pc.in libbitcoinconsensus: Add pkg-config support 2014-11-20 21:23:34 +00:00
Makefile.am Support gathering of code coverage data for RPC tests 2015-10-23 22:09:24 +02:00
README.md The Bitcoin Core project is releasing Bitcoin Core, not Bitcoin. 2015-10-05 21:20:43 +02:00

Bitcoin Core integration/staging tree

Build Status

https://www.bitcoin.org

What is Bitcoin?

Bitcoin is an experimental new digital currency that enables instant payments to anyone, anywhere in the world. Bitcoin uses peer-to-peer technology to operate with no central authority: managing transactions and issuing money are carried out collectively by the network. Bitcoin Core is the name of open source software which enables the use of this currency.

For more information, as well as an immediately useable, binary version of the Bitcoin Core software, see https://www.bitcoin.org/en/download.

License

Bitcoin Core is released under the terms of the MIT license. See COPYING for more information or see http://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

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

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 with: qa/pull-tester/rpc-tests.py

Every pull request is built for both Windows and Linux on a dedicated server, and unit and sanity tests are automatically run. The binaries produced may be used for manual QA testing — a link to them will appear in a comment on the pull request posted by BitcoinPullTester. See https://github.com/TheBlueMatt/test-scripts for the build/test scripts.

Manual Quality Assurance (QA) Testing

Large changes should have a test plan, and should be tested by somebody other than the developer who wrote the code. See https://github.com/bitcoin/QA/ for how to create a test plan.

Translations

Changes to translations as well as new translations can be submitted to Bitcoin Core's Transifex page.

Translations are periodically pulled from Transifex and merged into the git repository. See the translation process for details on how this works.

Important: We do not accept translation changes as GitHub pull requests because the next pull from Transifex would automatically overwrite them again.

Translators should also subscribe to the mailing list.