Commit b170e128 authored by intrigeri's avatar intrigeri
Browse files

Release process: take GitLab permissions model into account

RMs are not allowed to edit group milestones.

At some point I want us to figure out who can clone, and propose MRs against,
our gitlab-config repo.

Reported by kibi on
#17747 (comment 150112)
parent d99be50d
......@@ -1873,10 +1873,10 @@ If you just released a final release
<https://jenkins.tails.boum.org/>.
1. Make sure you pushed all changes in every of our Git repo (including our
Debian packages ones).
1. Set the *Due date* for the [[!tails_gitlab
1. Ask sysadmins to set the *Due date* for the [[!tails_gitlab
groups/tails/-/milestones
desc="*Holes in the Roof* milestone"]] to a date between
the next 2 releases.
the next 2 releases, via `gitlab-config.git`.
1. In [[contribute/calendar]], remove the entries about the version that you've
just released.
1. Check the Mozilla release calendars:
......
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