-Bitcoin TEST network source code
-================================
-Branches here:
+Bitcoin integration/staging tree
-* svn : up-to-date mirror of the 'production' Bitcoin (from http://sourceforge.net/projects/bitcoin/).
-* listtransactions: Implements new JSON-RPC command "listtransactions" (from jgarzik)
-* refundtransaction : Implements new JSON-RPC command "refundtransaction"
+Development process
+===================
-These branches operate on the TEST network:
+Developers work in their own trees, then submit pull requests when
+they think their feature or bug fix is ready.
-* svnTEST : just like 'svn' (no additional features), but patched to operate on the TEST network.
-* master : runs on the TEST-network with any of what I think are "production-ready" features.
+If it is a simple/trivial/non-controversial change, then one of the
+bitcoin development team members simply pulls it.
-Important changes on the master branch are:
+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
-* Listen port is 18333 (instead of 8333). Uses 18332 for JSON-RPC (instead of 8332).
-* Uses irc.lfnet.org channel #bitcoinTEST for bootstrapping.
-* Never tries to connect to "well known" nodes for bootstrapping.
-* Uses bitcoinTEST for the default data directory (e.g. ~/.bitcoinTEST on Linux, %APPDATA%/BitcoinTEST on Windows, etc)
-* Uses a different ADDRESSVERSION for Bitcoin Addresses (0xff instead of 0x0), so you can't screw up copying and pasting Bitcoin addresses (if you try to use a TEST address on the production system it will tell you it's invalid; you can, however, lose TESTcoins by trying to send them to a valid production address)
-* Has a brand-new block chain (with a different genesis block)
-* Initial difficulty is 4 times easier than production Bitcoin
-* protocol message header bytes are { 0xfa, 0xbf, 0xb5, 0xda } instead of { 0xf9, 0xbe, 0xb4, 0xd9 }
+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.
-Code is hosted at github: http://github.com/gavinandresen/bitcoin-git
+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.
+Feature branches are created when there are major new features being
+worked on by several people.
+
+From time to time a pull request will become outdated. If this occurs, and
+the pull is no longer automatically mergeable; a comment on the pull will
+be used to issue a warning of closure. The pull will be closed 15 days
+after the warning if action is not taken by the author. Pull requests closed
+in this manner will have their corresponding issue labeled 'stagnant'.
+
+Issues with no commits will be given a similar warning, and closed after
+15 days from their last activity. Issues closed in this manner will be
+labeled 'stale'.
+
+Requests to reopen closed pull requests and/or issues can be submitted to
+QA@BitcoinTesting.org.
\ No newline at end of file
git://git.novaco.in / novacoin.git / blobdiff