summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>2017-02-10 11:15:25 +0000
committerDmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>2017-02-10 11:15:25 +0000
commitde65731631c741db65cf6e6297715c936a7aaf10 (patch)
tree783572109e7def7e2258ce3101ee4d009a95bf2c
parentf60cb12f695f8da02ca7547e41e37e0f8dbb958d (diff)
parentfe04d920544c0234d22aa5a8c7c6793a99d3e267 (diff)
downloadgitlab-ce-de65731631c741db65cf6e6297715c936a7aaf10.tar.gz
Merge branch 'dz-patch-1' into 'master'
Add clarification to RC1 date See merge request !9104
-rw-r--r--PROCESS.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/PROCESS.md b/PROCESS.md
index f257c1d5358..fead93bd4cf 100644
--- a/PROCESS.md
+++ b/PROCESS.md
@@ -59,7 +59,7 @@ star, smile, etc.). Some good tips about code reviews can be found in our
## Feature Freeze
-On the 7th of each month, RC1 of the upcoming release is created and deployed to GitLab.com and the stable branch for this release is frozen, which means master is no longer merged into it.
+After the 7th (Pacific Standard Time Zone) of each month, RC1 of the upcoming release is created and deployed to GitLab.com and the stable branch for this release is frozen, which means master is no longer merged into it.
Merge requests may still be merged into master during this period,
but they will go into the _next_ release, unless they are manually cherry-picked into the stable branch.
By freezing the stable branches 2 weeks prior to a release, we reduce the risk of a last minute merge request potentially breaking things.