mirrors/bitcoin
1
0
Fork 0
mirror of https://github.com/bitcoin/bitcoin.git synced 2024-11-19 09:53:47 +01:00
Code Issues Projects Releases Wiki Activity
Bitcoin Core integration/staging tree
10,936 Commits 6 Branches 318 Tags 3.2 GiB
C++ 64%
Python 19.9%
C 12.4%
CMake 1.1%
Shell 0.9%
Other 1.6%
67db011e12
Go to file
Wladimir J. van der Laan 67db011e12
Merge #8177: developer notes: updates for C++11 
654a211 developer notes: updates for C++11 (Kaz Wesley)
2016-06-10 11:29:36 +02:00
.tx qt: translation update prior to opening 0.12 translations 2015-11-01 16:11:50 +01:00
build-aux/m4 build: update ax_cxx_compile_stdcxx to serial 4 2016-04-28 10:18:06 +02:00
contrib Merge #8180: Update luke-jr's PGP key 2016-06-09 16:44:16 +02:00
depends Merge #8167: gitian: Ship debug tarballs/zips with debug symbols 2016-06-09 07:13:14 +02:00
doc Merge #8177: developer notes: updates for C++11 2016-06-10 11:29:36 +02:00
qa Merge #8133: build: Finish up out-of-tree changes 2016-06-10 10:05:57 +02:00
share build: Get rid of CLIENT_DATE 2016-06-09 13:34:09 +02:00
src qt: translations update 2016-06-10 10:12:00 +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 travis: use out-of-tree build 2016-06-01 22:21:08 -04:00
autogen.sh autogen.sh: warn about needing autoconf if autoreconf is not found 2016-02-13 04:44:42 +08:00
configure.ac build: a few ugly hacks to get the rpc tests working out-of-tree 2016-06-01 20:31:55 -04:00
CONTRIBUTING.md [doc] Add basic git squash example 2016-05-10 16:14:21 +08:00
COPYING Update license year range to 2016 2016-01-17 23:38:11 +05:30
INSTALL Prettify some /Contrib READMEs 2013-10-21 20:07:31 -04:00
libbitcoinconsensus.pc.in Unify package name to as few places as possible without major changes 2015-12-14 02:11:10 +00:00
Makefile.am build: add temporary fix for "bad magic number" error in out-of-tree builds 2016-06-03 14:48:21 -04:00
README.md changing "(tests are) automatically run" to correspond to the earlier instance of "run automatically (on the build server)" 2016-05-09 14:00:28 +02:00

README.md

Bitcoin Core integration/staging tree

Build Status

https://bitcoincore.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://bitcoin.org/en/download, or read the original whitepaper.

License

Bitcoin 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 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 (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.

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.