Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

developement process updated in correspondence with .12.1 branch #839

Closed
wants to merge 1 commit into from
Closed

developement process updated in correspondence with .12.1 branch #839

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
22 changes: 5 additions & 17 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -27,27 +27,15 @@ License
Dash Core is released under the terms of the MIT license. See [COPYING](COPYING) for more
information or see http://opensource.org/licenses/MIT.

Development process
Development Process
-------------------

Developers work in their own trees, then submit pull requests when they think
their feature or bug fix is ready.
The `master` branch is meant to be stable. Development is normally done in separate branches.
[Tags](https://github.com/bitcoin/bitcoin/tags) are created to indicate new official,
stable release versions of Dash Core.

If it is a simple/trivial/non-controversial change, then one of the Dash
development team members simply pulls it.
The contribution workflow is described in [CONTRIBUTING.md](CONTRIBUTING.md).

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](https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev)

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
match the project's coding conventions (see [doc/coding.md](doc/coding.md)) or are
controversial.

The `master` branch is regularly built and tested, but is not guaranteed to be
completely stable. [Tags](https://github.com/dashpay/dash/tags) are created
regularly to indicate new official, stable release versions of Dash. ***TODO***

Testing
-------
Expand Down