-
Notifications
You must be signed in to change notification settings - Fork 29
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Jeff Garzik
authored and
Jeff Garzik
committed
Sep 6, 2011
1 parent
3a7c4d8
commit cc558f0
Showing
1 changed file
with
21 additions
and
6 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,15 +1,30 @@ | ||
|
||
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. | ||
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 | ||
|
||
If it is a simple/trivial/non-controversial change, then one of the bitcoin development team members simply pulls it. | ||
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. | ||
|
||
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 [email protected]. | ||
|
||
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 [email protected]. | ||
Feature branches are created 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. |