Release 1.50.0
teamDelivery is requesting a release of GitLab Pages to include the latest labkit version that includes some debug statements to assist with the troubleshooting of the Profiler, which currently is not working for .com. Reference: gitlab-com/gl-infra/production#6011 (closed)
-
Set the milestone on this issue - Decide on the version number by reference to
the Versioning
- Typically if you want to release code from current
master
branch you will updateMINOR
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
- Typically if you want to release code from current
-
Create an MR for gitlab-pages project. You can use this MR as an example. -
Update VERSION
, and push your branch -
Update CHANGELOG
by runningGITLAB_PRIVATE_TOKEN= make changelog
, note that you need to create a personal access token -
Assign to reviewer
-
-
Once gitlab-pages
is merged create a signed+annotated tag pointing to the merge commit on the stable branch In case ofmaster
branch:git fetch origin master git fetch dev master git tag -a -s -m "Release v1.0.0" v1.0.0 origin/master
stable
branch:git fetch origin 1-0-stable git fetch dev 1-0-stable git tag -a -s -m "Release v1.0.0" v1.0.0 origin/1-0-stable
-
Verify that you created tag properly: git show v1.0.0
-
(tag: v1.0.0, origin/master, dev/master, master)
formaster
-
(tag: v1.0.1, origin/1-0-stable, dev/1-0-stable, 1-0-stable)
forstable
branch
-
-
Push this tag to origin(Skip this for security release!) git push origin v1.0.0
-
Wait for tag to be mirrored to dev
or push it:git push dev v1.0.0
-
Create an MR for gitlab project. You can use this MR as an example. -
Update GITLAB_PAGES_VERSION
-
Added Changelog: added
footer to your commit -
Assign to a reviewer
-
Edited by Vladimir Shushlin