BigW Consortium Gitlab

Skip to content

G
gitlab-ce
Commit 13233d6d by Sytse Sijbrandij
Options

Merge branch 'regression-issue' into 'master'

Regression issue We want to aid communication between the issue tracker team and the release manager with this. A first example of this issue is https://gitlab.com/gitlab-org/gitlab-ce/issues/294
parents d4b61a67 17480733
Showing with 11 additions and 0 deletions
doc/release/monthly.md
......@@ -201,6 +201,17 @@ Include a link to the blog post and keep it short.
Proposed email for CE: "We have released a new version of GitLab Community Edition and its packages. See our blog post(<link>) for more information."
### **10. Create a regressions issue**
On [the GitLab CE issue tracker on GitLab.com](https://gitlab.com/gitlab-org/gitlab-ce/issues/) create an issue titled "GitLab X.X regressions" add the following text:
This is a meta issue to discuss possible regressions in this monthly release and any patch versions.
Please do not raise issues directly in this issue but link to issues that might warrant a patch release.
The decision to create a patch release or not is with the release manager who is assigned to this issue.
The release manager will comment here about the plans for patch releases.
Assign the issue to the release manager and /cc all the core-team members active on the issue tracker. If there are any known bugs in the release add them immediately.
# **23rd - Optional Patch Release**
# **24th - Update GitLab.com**
......
Markdown is supported
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