Skip to content
Newer
Older
100644 42 lines (31 sloc) 1.75 KB
cc558f0 README.md: word wrap text file
Jeff Garzik authored Sep 5, 2011
1
cba3a17 @gavinandresen Straw-man for dev process
gavinandresen authored Dec 19, 2010
2 Bitcoin integration/staging tree
81b2d87 @gavinandresen Update README.md
gavinandresen authored Sep 23, 2010
3
ae42d69 @gavinandresen Updated development process description
gavinandresen authored Jan 21, 2011
4 Development process
5 ===================
81b2d87 @gavinandresen Update README.md
gavinandresen authored Sep 23, 2010
6
cc558f0 README.md: word wrap text file
Jeff Garzik authored Sep 6, 2011
7 Developers work in their own trees, then submit pull requests when
8 they think their feature or bug fix is ready.
9
10 If it is a simple/trivial/non-controversial change, then one of the
11 bitcoin development team members simply pulls it.
12
13 If it is a more complicated or potentially controversial
14 change, then the patch submitter will be asked to start a
15 discussion (if they haven't already) on the mailing list:
16 http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development
cba3a17 @gavinandresen Straw-man for dev process
gavinandresen authored Dec 19, 2010
17
cc558f0 README.md: word wrap text file
Jeff Garzik authored Sep 6, 2011
18 The patch will be accepted if there is broad consensus that it is a
19 good thing. Developers should expect to rework and resubmit patches
20 if they don't match the project's coding conventions (see coding.txt)
21 or are controversial.
cba3a17 @gavinandresen Straw-man for dev process
gavinandresen authored Dec 19, 2010
22
cc558f0 README.md: word wrap text file
Jeff Garzik authored Sep 6, 2011
23 The master branch is regularly built and tested, but is not guaranteed
24 to be completely stable. Tags are regularly created to indicate new
25 official, stable release versions of Bitcoin. If you would like to
16d6963 @gavinandresen Fix QA email address
gavinandresen authored Sep 22, 2011
26 help test the Bitcoin core, please contact QA@BitcoinTesting.org.
cba3a17 @gavinandresen Straw-man for dev process
gavinandresen authored Dec 19, 2010
27
cc558f0 README.md: word wrap text file
Jeff Garzik authored Sep 6, 2011
28 Feature branches are created when there are major new features being
29 worked on by several people.
13945b2 @alexwaters Updated readme file with timers.
alexwaters authored Sep 26, 2011
30
31 From time to time a pull request will become outdated. If this occurs, and
32 the pull is no longer automatically mergeable; a comment on the pull will
33 be used to issue a warning of closure. The pull will be closed 15 days
34 after the warning if action is not taken by the author. Pull requests closed
35 in this manner will have their corresponding issue labeled 'stagnant'.
36
37 Issues with no commits will be given a similar warning, and closed after
38 15 days from their last activity. Issues closed in this manner will be
39 labeled 'stale'.
40
41 Requests to reopen closed pull requests and/or issues can be submitted to
42 QA@BitcoinTesting.org.
Something went wrong with that request. Please try again.