bitcoin code
What is Bitcoin?
Bitcoin is an experimental digital currency that enables instant payments to anyone, anywhere in the planet. Bitcoin uses peer-to-peer technology to operate with no central authority: managing transactions and issuing cash are distributed collectively by the network. bitcoin code is that the name of open source software that permits the utilization of this currency.
For more data, furthermore an immediately usable, binary version of the bitcoin code software, see https://bitcoincore.org/en/download/, or read the original whitepaper.
License
bitcoin code is released under the terms of the MIT license. See COPYING for more data or see https://opensource.org/licenses/MIT.
Development Method
The master branch is frequently designed (see doc/build-*.md for directions) and tested, but it is not guaranteed to be completely stable. Tags are created regularly from unleash branches to point new official, stable unleash versions of bitcoin code.
The https://github.com/bitcoin-core/gui repository is employed solely for the development of the GUI. Its master branch is identical in all monotree repositories. Unharness branches and tags do not exist, therefore please do not fork that repository unless it's for development reasons.
The contribution workflow is described in CONTRIBUTING.md and helpful hints for developers can be found in doc/developer-notes.md.
Testing
Testing and code review is the bottleneck for development; we get a lot of pull requests than we tend to will review and check on short notice. Please wait and facilitate out by testing different folks's pull requests, and bear in mind this is often a security-important project where any mistake would possibly price folks heaps of cash.
Automated Testing
Developers are strongly inspired to write down unit tests for new code, and to submit new unit tests for old code. Unit tests will be compiled and run (assuming they weren't disabled in configure) with: create check. Further details on running and lengthening unit tests will be found in /src/take a look at/README.md.
There are regression and integration tests, written in Python, that are run automatically on the build server. These tests will be run (if the take a look at dependencies are put in) with: check/useful/check_runner.py
The Travis CI system makes sure that each pull request is constructed for Windows, Linux, and macOS, and that unit/sanity tests are run automatically.
Manual Quality Assurance (QA) Testing
Changes should be tested by somebody different than the developer who wrote the code. This is often particularly necessary for large or high-risk changes. It's useful to add a check arrange to the pull request description if testing the changes isn't simple.
Translations
Changes to translations as well as new translations can be submitted to bitcoin code's Transifex page.
Translations are periodically pulled from Transifex and merged into the git repository. See the translation method for details on how this works.
Necessary: We tend to do not settle for translation changes as GitHub pull requests as a result of the following pull from Transifex would automatically overwrite them again.
Translators ought to conjointly subscribe to the mailing list.
Comments
Post a Comment