Prepare internal comms for developers and release managers
To gather early feedback into the new process and release tooling associated with the extension of the maintenance policy, starting from 2023-03-22, stable branches will be opened to engineers allowing them to self-serve and merge bug fixes at will, while release managers continue to patch only the current version.
This issue is to define the internal comms for developers and release managers. One issue should be opened for engineers and another one for release managers to announce and explain the new process
Engineers
The issue for Engineers should cover:
- Process to follow: Merge request on GitLab canonical, approvals, package-and-test execution
- Restrictions: Bug fixes only.
- Maintenance policy details:
- Highlight what is changing
- Comparison to the current workflow (pick into vs merging)
- What versions can patch releases be expected for?
- When the maintenance policy is going to be updated.
- Release processes:
- State the security release process stays the same
- State the monthly release process stays the same
Release managers
The issue for Release managers should cover:
- How to read the patch release from the release manager dashboard.
- How to execute patch releases with the new code
- When the maintenance policy is going to be updated.
Implementation details
Engineers
-
Prepare an announcement issue #2886 (closed) -
Announce this internally on 2023-03-08 -
Post a message on whats-happening-at-gitlab
-
Use /chatops notify
-
Broadcast the message on #eng-managers
-
Broadcast the message on #product
. -
Broadcast the message on #quality
. Let them know this will result in SETs being pinged to review MRs targeting stable branch.
-
-
Add the message to Engineering Week in Review
Release managers
-
Prepare an announcement - #2863 (comment 1313729929) -
Create the issue - #2902 (closed)
Edited by Mayra Cabrera