From a24b23622e504f5134dd8011af5bbe68cb9443f1 Mon Sep 17 00:00:00 2001 From: "Wladimir J. van der Laan" Date: Fri, 15 Jul 2011 15:42:02 +0200 Subject: move README.md out of the way for now --- README.md | 16 ---------------- 1 file changed, 16 deletions(-) delete mode 100644 README.md (limited to 'README.md') diff --git a/README.md b/README.md deleted file mode 100644 index ab328adbff..0000000000 --- a/README.md +++ /dev/null @@ -1,16 +0,0 @@ -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. -- cgit v1.2.3 From 0465c41c847ddee7eeb5caefb164149400ff8395 Mon Sep 17 00:00:00 2001 From: "Wladimir J. van der Laan" Date: Sun, 18 Sep 2011 11:55:41 +0200 Subject: move current qt specific readme to doc/, restore original README.md --- README.md | 29 +++++++++++++++++++++++++++++ 1 file changed, 29 insertions(+) create mode 100644 README.md (limited to 'README.md') diff --git a/README.md b/README.md new file mode 100644 index 0000000000..67fa93d371 --- /dev/null +++ b/README.md @@ -0,0 +1,29 @@ + +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: +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, 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. -- cgit v1.2.3