diff options
author | Vladimir Shushlin <vshushlin@gitlab.com> | 2020-01-23 11:40:46 +0300 |
---|---|---|
committer | Alessio Caiazza <acaiazza@gitlab.com> | 2020-01-23 11:40:46 +0300 |
commit | e377ace0c44175f675cb84e4b96f29243cc4ed97 (patch) | |
tree | 54aae0c17a851181f2841be40434fc55a35b6706 /PROCESS.md | |
parent | 030060877e2901912d98e0fdc200743d3b9f59aa (diff) |
Move release instructions into issue template
Diffstat (limited to 'PROCESS.md')
-rw-r--r-- | PROCESS.md | 31 |
1 files changed, 2 insertions, 29 deletions
@@ -19,35 +19,8 @@ rewritten. Tags should never be deleted. Pages is tightly coupled to GitLab itself. To align with GitLab's [development month](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/PROCESS.md), new versions of GitLab Pages are released before the 7th of each month (assuming -any changes have been made). To do so: - -1. For major and minor releases, create a stable branch if it doesn't already exist: - - ```shell - git checkout -b X-Y-stable master # MAJOR.MINOR - git push https://gitlab.com/gitlab-org/gitlab-pages.git X-Y-stable - git push https://dev.gitlab.org/gitlab/gitlab-pages.git X-Y-stable - ``` - -1. Review the list of changes since the last release and create a changelog -1. Decide on the version number by reference to the [Versioning](#versioning) section -1. [Create a new issue](https://gitlab.com/gitlab-org/gitlab-pages/issues/new) containing the changelog -1. Create a new merge request, modifying the `CHANGELOG` and `VERSION` files, targeting the correct stable branch -1. Once it's merged, create a signed+annotated tag pointing to the **merge commit** on the **stable branch**, e.g.: - - ```shell - git fetch origin 1-0-stable - git tag -a -s -m "Release v1.0.0" v1.0.0 origin/1-0-stable - git push https://gitlab.com/gitlab-org/gitlab-pages.git v1.0.0 - git push https://dev.gitlab.org/gitlab/gitlab-pages.git v1.0.0 - ``` - -1. Create a merge request against [GitLab](https://gitlab.com/gitlab-org/gitlab-ce) to update `GITLAB_PAGES_VERSION` - -As each release is made, the `CHANGELOG` for the stable branch will be updated -to contain content not in the **master** branch. To resolve this, the stable -branches may be merged to **master**. For more complicated merges, it may be -easier to pick just the updates to `CHANGELOG`. +any changes have been made). +To do so create [release issue](https://gitlab.com/gitlab-org/gitlab-pages/issues/new?issuable_template=release) and follow the instructions. ## Stable releases |