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: [PATCH] move README.md out of the way for now --- README-original.md | 16 ++++++++++++++++ README.md | 16 ---------------- 2 files changed, 16 insertions(+), 16 deletions(-) create mode 100644 README-original.md delete mode 100644 README.md diff --git a/README-original.md b/README-original.md new file mode 100644 index 0000000..ab328ad --- /dev/null +++ b/README-original.md @@ -0,0 +1,16 @@ +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. diff --git a/README.md b/README.md deleted file mode 100644 index ab328ad..0000000 --- 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. -- 1.7.1