+
Bitcoin integration/staging tree
-Straw-man plan for Bitcoin development (open source vets, please slap me around and help make this better):
+Development process
+===================
+
+Developers work in their own trees, then submit pull requests when
+they think their feature or bug fix is ready.
-Developers work in their own trees, then submit pull requests when they think their feature is ready.
+If it is a simple/trivial/non-controversial change, then one of the
+bitcoin development team members simply pulls it.
-Requests get discussed (where? bitcoin forums?) and if there's broad consensus they're a good thing, well written, match coding style, etc. then they're merged into the 'master' branch.
+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
-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 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 QA@BitcoinTesting.org.
-We'll create feature branches if/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.
git://git.novaco.in / novacoin.git / blobdiff