Announcement: Cadence of deployment to GitLab.com and environments is changing

What is changing?

Starting from 2020-02-02, the cadence of auto-deploy branches will change from once a week to two times a week. This means that all changes in master branch of gitlab-org/gitlab will be reaching GitLab.com and the environments more frequently.

How does this impact me?

If you are a part of:

• Engineering group (part of any department that works with GitLab.com)
• Product group

this change has a potential of impacting your workflow.

Any change, including features, merged into master branch of gitlab-org/gitlab will be deployed to staging, canary and GitLab.com environments more frequently than previously.

Previously, all non-urgent changes merged into master were deployed the following week.

Going forward, all non-urgent changes merged into master will be deployed:

1. the same week if merged between Sunday and end of the work day Tuesday
2. the following week if merged to master between start of Wednesday and Sunday.

Additional information

Please consult the releases handbook page for GitLab.com releases for complete set of information.

added Announcements teamDelivery labels

marked this issue as related to #627 (closed)

assigned to @marin

Sunday and end of the work day Tuesday...

Is it possible to know what timezone we follow for these days?

We use UTC as all of our infrastructure and pipelines observe UTC.

New auto-deploy branches will be created from master on Sunday and on Wednesday at 4:00 am UTC #627 (comment 270851026) .

FYI @gl-quality

mentioned in merge request gitlab-org/gitlab!22808 (merged)

closed

mentioned in issue scalability#149

mentioned in merge request gitlab-org/gitlab!25110 (merged)

mentioned in issue #815 (closed)

mentioned in issue #2143 (closed)