Commit 13233d6d1e421e16d5c1ae6386a89d44793102c9
Exists in
spb-stable
and in
2 other branches
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
Showing
1 changed file
with
11 additions
and
0 deletions
Show diff stats
doc/release/monthly.md
| @@ -201,6 +201,17 @@ Include a link to the blog post and keep it short. | @@ -201,6 +201,17 @@ Include a link to the blog post and keep it short. | ||
| 201 | 201 | ||
| 202 | 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." | 202 | 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." |
| 203 | 203 | ||
| 204 | +### **10. Create a regressions issue** | ||
| 205 | + | ||
| 206 | +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: | ||
| 207 | + | ||
| 208 | +This is a meta issue to discuss possible regressions in this monthly release and any patch versions. | ||
| 209 | +Please do not raise issues directly in this issue but link to issues that might warrant a patch release. | ||
| 210 | +The decision to create a patch release or not is with the release manager who is assigned to this issue. | ||
| 211 | +The release manager will comment here about the plans for patch releases. | ||
| 212 | + | ||
| 213 | +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. | ||
| 214 | + | ||
| 204 | # **23rd - Optional Patch Release** | 215 | # **23rd - Optional Patch Release** |
| 205 | 216 | ||
| 206 | # **24th - Update GitLab.com** | 217 | # **24th - Update GitLab.com** |