Transparent planning within Development

Why is this change being made?

From the development staff meeting (internal only link):

With high level reporting on what each of the groups are planning for a release, we can increase the situational awareness of development leadership which will help us understand the context of higher priority requests, be transparent about the tradeoffs we are making, and surface which teams would be able more capable of helping on certain topics.

As an example, your team may have already planned several P1/S1 issues when an urgent request comes in to be worked immediately. These high level reports will help provide an understanding of the situation this team now faces, so that a better decision can be made in terms of the competing priorities.

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
  • Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added.
• Assign reviewers for this change to the correct DRI(s)
  • If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the "Maintained by" section in on the page being edited.
  • 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.
• If the changes affect team members, or warrant an announcement in another way, please consider posting an update in #whats-happening-at-gitlab linking to this MR.
  • If this is a change that directly impacts the majority of global team members, it should be a candidate for #company-fyi. Please work with internal communications and check the handbook for examples.

---