Difference between revisions of "Development process"

From Bitcoin Wiki
Jump to: navigation, search
(Bitcoin Core Open Source Development Process: Add paragraph from Bitcoin project repo about contributing.)
(Bitcoin Core Open Source Development Process: Update since Sourceforge is no longer part of the process.)
Line 7: Line 7:
 
# When a developer thinks a patch is ready, they submit a pull request for the [https://github.com/bitcoin/bitcoin bitcoin github repository] and post a message on the [https://bitcointalk.org/index.php?board=6.0 Development and Technical Forum].
 
# When a developer thinks a patch is ready, they submit a pull request for the [https://github.com/bitcoin/bitcoin bitcoin github repository] and post a message on the [https://bitcointalk.org/index.php?board=6.0 Development and Technical Forum].
 
# Pull requests are discussed on the forums and if there is consensus they're safe, tested, useful, well written, match coding style, etc. then they're merged into the 'master' branch.
 
# Pull requests are discussed on the forums and if there is consensus they're safe, tested, useful, well written, match coding style, etc. then they're merged into the 'master' branch.
# The master github branch is regularly built and tested, and periodically pushed to the [http://sourceforge.net/projects/bitcoin/develop subversion repository] to become a "release candidate" and then the official, stable, released bitcoin.
+
# The master github branch is regularly built and tested, and periodically given a "release candidate" tag followed by a version tag which is then an official, stable Bitcoin Core release.
 
# After being accepted into the mainline master branch, bugfixes are merged or backported into the current stable branch, which periodically releases stable older versions.
 
# After being accepted into the mainline master branch, bugfixes are merged or backported into the current stable branch, which periodically releases stable older versions.
  

Revision as of 13:17, 27 September 2015

Bitcoin Core Open Source Development Process

The Bitcoin Core project operates an open contributor model where anyone is welcome to contribute towards development in the form of peer review, testing and patches.

Bitcoin Core has transitioned from what was essentially a one-person software endeavor, with Satoshi functioning as the primary developer and gatekeeper for all changes, to a more distributed, free software model of development with hundreds of contributors. The Linux Kernel development process is being used as the model for how changes flow into the original Bitcoin application:

  1. Developers work in their own source code trees, sharing and testing patches with each other. Git, using github, is the preferred source control system for development.
  2. When a developer thinks a patch is ready, they submit a pull request for the bitcoin github repository and post a message on the Development and Technical Forum.
  3. Pull requests are discussed on the forums and if there is consensus they're safe, tested, useful, well written, match coding style, etc. then they're merged into the 'master' branch.
  4. The master github branch is regularly built and tested, and periodically given a "release candidate" tag followed by a version tag which is then an official, stable Bitcoin Core release.
  5. After being accepted into the mainline master branch, bugfixes are merged or backported into the current stable branch, which periodically releases stable older versions.

Please read and follow coding.txt for a description of the bitcoin coding style.

See Also