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 b53e277ba1 Stay connected to seed nodes; disconnecting causes problems if you are trying to make the initial blockchain download. 11 years ago
contrib Add reference python miner, in contrib/pyminer/ 11 years ago
doc Fix typo ("you own security") 11 years ago
locale Merge pull request #475 from ovdeathiam/patch-1 11 years ago
share Make it clear that setting proxy requires restart to fully apply. 11 years ago
src Stay connected to seed nodes; disconnecting causes problems if you are trying to make the initial blockchain download. 11 years ago
.gitignore Add common temp files to .gitignore. 12 years ago
COPYING
README
README.md

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.