Commit fbad32f1 authored by Sytse Sijbrandij's avatar Sytse Sijbrandij
Browse files

Include release candidates in the monthly release process.

parent bfe4c494c09b
...@@ -58,9 +58,11 @@ ...@@ -58,9 +58,11 @@
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. 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 * 5 days before release: feature freeze (stop merging new features)
* 3 days before release: UI freeze * 4 days before release: UI freeze (stop merging changes to the user interface)
* 1 day before release: code freeze * 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 # Write a blog post
...@@ -73,4 +75,4 @@ ...@@ -73,4 +75,4 @@
1. Update VERSION and CHANGELOG 1. Update VERSION and CHANGELOG
1. Create a git tag vX.X.X 1. Create a git tag vX.X.X
1. Publish the blog post 1. Publish the blog post
1. Tweet about the release 1. Tweet about the release
\ No newline at end of file
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment