aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRiccardo Spagni <ric@spagni.net>2017-12-02 09:26:31 +0200
committerRiccardo Spagni <ric@spagni.net>2017-12-02 09:26:32 +0200
commitbacbc0705f2f6245b5662dd3b94918a2e67dbee0 (patch)
treea0d58ac1805f1ca859e6b31f6d4bdfa2b44b4910
parentMerge pull request #2836 (diff)
parentUpdate README.md with info about release timelines (diff)
downloadmonero-bacbc0705f2f6245b5662dd3b94918a2e67dbee0.tar.xz
Merge pull request #2843
26ce640f Update README.md with info about release timelines (Gingeropolous)
-rw-r--r--README.md4
1 files changed, 4 insertions, 0 deletions
diff --git a/README.md b/README.md
index 0d243f0cc..4386aacaa 100644
--- a/README.md
+++ b/README.md
@@ -111,6 +111,10 @@ Dates are provided in the format YYYY-MM-DD.
X's indicate that these details have not been determined as of commit date, 2017-09-20.
+## Monero release staging schedule and protocol
+
+Approximately 3 months prior to a Network Consensus Protocol Upgrade, a branch from Master will be created with the new release version tag. Pull requests that address bugs should then be made to both Master and the new release branch. Pull requests that require extensive review and testing (generally, optmizations and new features) should *not* be made to the release branch.
+
## Installing Monero from a Package
Packages are available for