You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Wladimir J. van der Laan 223b6f1ba4 make bitcoin include files more modular 10 years ago
contrib gitian: strip binaries 10 years ago
doc Manual merge of jaromil's source tree reorg commit. 10 years ago
locale Remove GUI's "Generate Coins" option from the menu. 10 years ago
share Fix MinGW build due to bad pointers to ui.rc pixmaps stuff. 10 years ago
src make bitcoin include files more modular 10 years ago
.gitignore directory re-organization (keeps the old build system) 10 years ago
COPYING directory re-organization (keeps the old build system) 10 years ago
README directory re-organization (keeps the old build system) 10 years ago
README.md Updated development process description 10 years ago

README.md

Bitcoin integration/staging tree

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 development forums: http://www.bitcoin.org/smf/index.php?board=6.0 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 they don’t match the project’s coding conventions (see coding.txt) or are controversial.

The master branch is regularly built and tested (by who? need people willing to be quality assurance testers), and periodically pushed to the subversion repo to become the official, stable, released bitcoin.

Feature branches are created when there are major new features being worked on by several people.