Create a LevelUp Training for early branch and monthly release
The Automate the creation of monthly releases in pr... (gitlab-com/gl-infra/software-delivery&1 - closed) and Extend the maintenance policy to account for th... (&971 - closed) involve a new release era with multiple changes for GitLab internals stakeholders.
The purpose of this issue is to create LevelUp content to increase and measure engagement with GitLab internal uses about these changes https://handbook.gitlab.com/handbook/people-group/learning-and-development/level-up/
From #21095 (comment 2554315191)
We can make LevelUp content, but may need permissions via Access Request: Content is: SmartCard ~ 1 video/demo, Pathway - group of smartcards, Journey - group of pathways.
Handbook links:
Rolling out a new monthly process should be broadcast and acknowledged by multiple GitLab folks. One way to achieve this is to create a course on LevelUp explaining:
- The new GitLab monthly process
- Release terminology
- Monthly and patch release cadence
- How to validate if changes are included in a monthly or a patch
- Maintenance policy updates &971 (closed)
The training should highlight:
- one-time effect: The release when we introduce the early monthly change will be one week shorter
- recurring-effect: features deployed to gitlab.com after the 2nd Tuesday of the month, will not be part of the monthly release