Browse Source

Updated readme file

pull/1/head
Alex Waters 11 years ago
parent
commit
adb8a55b46
  1. 7
      README.md

7
README.md

@ -7,10 +7,9 @@ Developers work in their own trees, then submit pull requests when they think th @@ -7,10 +7,9 @@ Developers work in their own trees, then submit pull requests when they think th
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
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: http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development
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.
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 QA@Bitcoin.org.
Feature branches are created when there are major new features being worked on by several people.
Feature branches are created when there are major new features being worked on by several people.
Loading…
Cancel
Save