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.
Gavin Andresen 7464e647de Bumped version numbers to 0.4.0rc1 10 lat temu
contrib Bumped version numbers to 0.4.0rc1 10 lat temu
doc Bumped version numbers to 0.4.0rc1 10 lat temu
locale Update binary mos to latest translations. 10 lat temu
share Bumped version numbers to 0.4.0rc1 10 lat temu
src Bumped version numbers to 0.4.0rc1 10 lat temu
.gitignore Add common temp files to .gitignore. 10 lat temu
COPYING directory re-organization (keeps the old build system) 10 lat temu
README directory re-organization (keeps the old build system) 10 lat temu
README.md Updated development process description 11 lat temu

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.