Skip to content

Update planning process

Patrick Bajaorequested to merge
pb-update-source-code-planning into master

Why is this change being made?

A proposal has been made months ago about planning upcoming milestone ahead (gitlab-org/create-stage#12641 (closed)).

We've tried and tested the proposed process for 3 releases and so far most of us like to continue it (gitlab-org/create-stage#12707 (closed)).

Author Checklist

  • Provided a concise title for the MR
  • Added a description to this MR explaining the reasons for the proposed change, per [say-why-not-just-what][transparency]
  • Assign this change to the correct DRI
    • If the DRI for the page/s being updated isn’t immediately clear, then assign it to your manager.
    • If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in [#mr-buddies][mr-buddies-slack].
    • If the changes relate to any part of the project other than updates to content and/or data files please make sure to ping @gl-static-site-editor in a comment for a review and merge. For example changes to .gitlab-ci.yml, JavaScript/CSS/Ruby code or the layout files.

Merge request reports