summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorSytse Sijbrandij <sytse@gitlab.com>2013-12-27 13:15:07 +0000
committerSytse Sijbrandij <sytse@gitlab.com>2013-12-27 13:15:07 +0000
commit3333d8b87b157baa3420a1028257b93cdb1ef993 (patch)
tree19844d6a5c444278b18e20925dcf39c2cc6f8ab3
parent3998bb3abad41abf6ba67ee04c37bdfc48e9313e (diff)
downloadgitlab-ce-3333d8b87b157baa3420a1028257b93cdb1ef993.tar.gz
Include release candidates in the monthly release process.
-rw-r--r--doc/release/monthly.md10
1 files changed, 6 insertions, 4 deletions
diff --git a/doc/release/monthly.md b/doc/release/monthly.md
index 1e56e080675..b96ae211812 100644
--- a/doc/release/monthly.md
+++ b/doc/release/monthly.md
@@ -58,9 +58,11 @@ Check if changed since last release (~22nd of last month depending on when last
After making the release branch new commits are cherry-picked from master. When the release gets closer we get more selective what is cherry-picked.
-* 5 days before release: feature freeze
-* 3 days before release: UI freeze
-* 1 day before release: code freeze
+* 5 days before release: feature freeze (stop merging new features)
+* 4 days before release: UI freeze (stop merging changes to the user interface)
+* 3 days before release: code freeze (stop merging non-essential code improvements)
+* 2 days before release: release candidate 1 (tag and tweet about x.x.rc1)
+* 1 day before release: release candidate 2 (optional, only if rc1 had problems)
# Write a blog post
@@ -73,4 +75,4 @@ After making the release branch new commits are cherry-picked from master. When
1. Update VERSION and CHANGELOG
1. Create a git tag vX.X.X
1. Publish the blog post
-1. Tweet about the release
+1. Tweet about the release \ No newline at end of file