Early branch creation: Internal Announcement

Context

The monthly release process does not allow enough time for QA or emergency fixes before the final release. The code that will be released to our customers is tested in production only for a few hours, and only with the specific configuration and feature flags we have on GitLab.com, resulting in bugs shipping with the monthly release and poor customer experience.

Automate the creation of monthly releases in pr... (gitlab-com/gl-infra/software-delivery&1 - closed) will move the active stable branch generation one week earlier in the release schedule to allow for thorough testing and timely backports. This will increase the quality, safety, and reliability of the monthly release while enabling a better developer experience and confidence.

Prepare an internal announcement for the early branch creation

gitlab-com/gl-infra/software-delivery&1 (closed), the early branch creation will be applicable for all upcoming releases, the purpose of this issue is to broadcast this information broadly

  • Prepare an internal announcement
  • Share the announcement on multiple Slack channels: #whats-happening-at-gitlab, #engineering-fyi, #development, #backend, #frontend, #releases
  • Add the announcement to the engineering-fyi document
  • Blog post?