Welcome to mirror list, hosted at ThFree Co, Russian Federation.

gitlab.com/gitlab-org/gitlab-pages.git - Unnamed repository; edit this file 'description' to name the repository.
summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJaime Martinez <jmartinez@gitlab.com>2022-02-22 00:26:29 +0300
committerJaime Martinez <jmartinez@gitlab.com>2022-02-22 00:26:29 +0300
commit33fc8c24381f3d3aafdf3f16c5a2b65104ac3cf3 (patch)
tree60e4854787b1451e943209e190d09df7e8a8244a
parent7c0e94be67c3103b4ef4e336f688c9674cb92740 (diff)
parent9ab613d5a55b5eabb5f3e57d342e96e100997057 (diff)
Merge branch 'docs-stable-branch' into 'master'
docs: add notes regarding stable branch creation to the release template Closes gitlab-org/security/gitlab#164 See merge request gitlab-org/gitlab-pages!702
-rw-r--r--.gitlab/issue_templates/release.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/.gitlab/issue_templates/release.md b/.gitlab/issue_templates/release.md
index 930508c8..3a4efc58 100644
--- a/.gitlab/issue_templates/release.md
+++ b/.gitlab/issue_templates/release.md
@@ -2,7 +2,7 @@
- Decide on the version number by reference to
the [Versioning](https://gitlab.com/gitlab-org/gitlab-pages/blob/master/PROCESS.md#versioning)
* Typically if you want to release code from current `master` branch you will update `MINOR` version, e.g. `1.12.0` -> `1.13.0`. In that case you **don't** need to create stable branch
- * If you want to backport some bug fix or security fix you will need to update stable branch `X-Y-stable`
+ * If you want to backport some bug fix or security fix you will need to create a stable branch `X-Y-stable` on the [security project](https://gitlab.com/gitlab-org/security/gitlab-pages). You will need maintainer access to create the stable branch.
- [ ] Create an MR for [gitlab-pages project](https://gitlab.com/gitlab-org/gitlab-pages).
You can use [this MR](https://gitlab.com/gitlab-org/gitlab-pages/merge_requests/217) as an example.
- [ ] Update `VERSION`, and push your branch