Development: Difference between revisions
Jump to navigation
Jump to search
Describe dev process |
|||
| Line 8: | Line 8: | ||
# The master github branch is regularly built and tested, and periodically pushed to the 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 pushed to the subversion repository to become a "release candidate" and then the official, stable, released bitcoin. | ||
Please read and follow [https://github.com/bitcoin/bitcoin/blob/master/coding.txt coding.txt] for a description of the bitcoin coding style. | |||
Revision as of 16:04, 3 January 2011
Bitcoin Open Source Development Process
January, 2011
Bitcoin is transitioning from what was essentially a one-person software project, with Satoshi functioning as the primary developer and gatekeeper for all changes, to a more distributed, open-source model of development. The Linux Kernel development process is being used as the model for how changes flow into the official Bitcoin application:
- 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.
- 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.
- 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 subversion repository to become a "release candidate" and then the official, stable, released bitcoin.
Please read and follow coding.txt for a description of the bitcoin coding style.