Create Runtime Update Process WG
Why is this change being made?
Establish the Runtime Update Process Working Group. The Slack channel and related Epic already existed.
The Business Goal
for the WG page probably states the purpose best:
We need to streamline the Golang runtime (version) update process which has been cumbersome and undocumented. Language framework updates are driven by multiple teams. In the case of Go, a half dozen or more teams are involved. The current Go upgrade process is difficult to execute at scale and requires manual intervention with a high degree of complexity. Goals include, but are not limited to:
- Create a streamlined Golang runtime (version) update process or possibly a language framework agnostic process
- Reduce update process complexity
- Create documentation around the update process to improve efficiency
- Increase developer and management efficiency
Outstanding Tasks
Here are the tasks needed before we can merge this MR to create the WG:
-
Create a label for the working group -
Create and issue board -
Identify an executive sponsor -
Identify a functional lead -
Define exit criteria
Author Checklist
-
Provided a concise title for this Merge Request (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 MR to the correct Directly Responsible Individual/s (DRI) - 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 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 DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the
-
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.
Edited by Matt Nohr