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 b7598ceefa Merge pull request #505 from gavinandresen/unique_coinbase 11 years ago
contrib Fix build process to actually work. 11 years ago
doc Bumped version numbers to 0.4.0rc1 11 years ago
locale Add binary mo for new translation. 11 years ago
share Bumped version numbers to 0.4.0rc1 11 years ago
src Merge branch 'unique_coinbase' of git:// into unique_coinbase 11 years ago
.gitignore ignore stuff 11 years ago
README word wrap text file 11 years ago

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 mailing list:

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, but is not guaranteed to be completely stable. Tags are regularly created to indicate new official, stable release versions of Bitcoin. If you would like to help test the Bitcoin core, please contact

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