|
|
|
@ -37,8 +37,7 @@ If it is a simple/trivial/non-controversial change, then one of the Litecoin |
|
|
|
development team members simply pulls it. |
|
|
|
development team members simply pulls it. |
|
|
|
|
|
|
|
|
|
|
|
If it is a *more complicated or potentially controversial* change, then the patch |
|
|
|
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 |
|
|
|
submitter will be asked to start a discussion with the devs and community. |
|
|
|
[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. |
|
|
|
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 the code doesn't |
|
|
|
Developers should expect to rework and resubmit patches if the code doesn't |
|
|
|
@ -46,7 +45,7 @@ match the project's coding conventions (see `doc/coding.txt`) or are |
|
|
|
controversial. |
|
|
|
controversial. |
|
|
|
|
|
|
|
|
|
|
|
The `master` branch is regularly built and tested, but is not guaranteed to be |
|
|
|
The `master` branch is regularly built and tested, but is not guaranteed to be |
|
|
|
completely stable. [Tags](https://github.com/bitcoin/bitcoin/tags) are created |
|
|
|
completely stable. [Tags](https://github.com/litecoin-project/litecoin/tags) are created |
|
|
|
regularly to indicate new official, stable release versions of Litecoin. |
|
|
|
regularly to indicate new official, stable release versions of Litecoin. |
|
|
|
|
|
|
|
|
|
|
|
Testing |
|
|
|
Testing |
|
|
|
|
whitj00
11 years ago