aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGingeropolous <Gingeropolous@users.noreply.github.com>2017-11-19 13:16:34 -0500
committerGitHub <noreply@github.com>2017-11-19 13:16:34 -0500
commit26ce640f8251073281ad4263dddd6a623ba17aea (patch)
treed2ae0bbf0ff1ebd22bfff1a0fdf620b7b3c52ec6
parentMerge pull request #2818 (diff)
downloadmonero-26ce640f8251073281ad4263dddd6a623ba17aea.tar.xz
Update README.md with info about release timelines
Added a heading in the readme that describes the release staging schedule and protocol.
-rw-r--r--README.md4
1 files changed, 4 insertions, 0 deletions
diff --git a/README.md b/README.md
index 2dec65465..082308e2d 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