1cd7952dde
45bfa13PARTIAL: typofixes (found by misspell_fixer) (Veres Lajos)21c406eadd support for miniupnpc api version 14 (Pavel Vasin)13bd5a7rpc-tests: re-enable rpc-tests for Windows (Cory Fields)ccc4ad6net: Set SO_REUSEADDR for Windows too (Cory Fields)1f6772eadd unit test for CNetAddr::GetGroup. (Alex Morcos)13642a5Fix masking of irrelevant bits in address groups. (Alex Morcos)6b51b9bReplace boost::reverse_lock with our own. (Casey Rodarmor)626c5e6Make sure we re-acquire lock if a task throws (Casey Rodarmor)4877053Add missing files to files.md (fanquake)f171feeHandle leveldb::DestroyDB() errors on wipe failure (Adam Weiss)c5b89feFix race condition on test node shutdown (Casey Rodarmor)4a37410Handle no chain tip available in InvalidChainFound() (Ross Nicoll)f6d29a6Use unique name for AlertNotify tempfile (Casey Rodarmor)e6adac7Delay initial pruning until after wallet init (Adam Weiss)e0020d4Make sure LogPrint strings are line-terminated (J Ross Nicoll)7ff9d12Make sure LogPrintf strings are line-terminated (Wladimir J. van der Laan)5a39133build: fix libressl detection (Cory Fields)f6355e6Avoid leaking file descriptors in RegisterLoad (Casey Rodarmor)60457d3locking: fix a few small issues uncovered by -Wthread-safety (Cory Fields)a496e11Remove bash test note from rpc-tests readme (fanquake)49c6a64tests: Remove old sh-based test framework (Wladimir J. van der Laan)a37567dAdd autogen.sh to source tarball. (randy-waterhouse)1f4d7cftravis: for travis generating an extra build (Cory Fields)
Bitcoin Core integration/staging tree
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
Developers work in their own trees, then submit pull requests when they think their feature or bug fix is ready.
If it is a simple/trivial/non-controversial change, then one of the Bitcoin development team members simply pulls it.
If it is a more complicated or potentially controversial change, then the patch submitter will be asked to start a discussion (if they haven't already) on the mailing list
The patch will be accepted if there is broad consensus that it is a good thing. Developers should expect to rework and resubmit patches if the code doesn't match the project's coding conventions (see doc/developer-notes.md) or are controversial.
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.
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
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.