Create a Release Artifacts working group

Why is this change being made?

💡 Provide a detailed answer to the question on why this change is being proposed, in accordance with our value of Transparency.

This MR sets up a new working group to create a specification for release artifacts

Context

The following Wardley map describes the current state and expected evolution of the application delivery market. @swiskow and @nagyv-gitlab discuss the map. The discussion recording is available here.

In terms of market dynamics, we identified that all the current tools, initiatives and projects we are aware of focus on a subset of the overall problem, and this is especially true at the beginning of the value chain. While every release process needs some form of a release artifact, there is no widely adopted specification to describe a release artifact. The Release Artifacts WG would try to fill this void setting up GitLab as a best in class application delivery tool and supporting our open-source ethos at the same time.

Prior art in GitLab issues

• Connection between releases and environments/de... (gitlab-org/gitlab#332103)
• Release as an input to a pipeline (gitlab-org/gitlab#332897)

TODO

• Get an exec sponsor
• Set up the team (facilitators, functional leads, members)
• Create the necessary artifacts
  • Slack
  • Notes doc
  • Epic

Author and Reviewer Checklist

Please verify the check list and ensure to tick them off before the MR is merged.

• 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, and the content is SAFE
• 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
  • The when to get approval handbook section explains the workflow in more detail
• For transparency, share this MR with the audience that will be impacted.
  • Team: For changes that affect your direct team, share in your group Slack channel
  • Department: If the update affects your department, share the MR in your department Slack channel
  • Company: If the update affects all (or the majority of) GitLab team members, post an update in #whats-happening-at-gitlab linking to this MR
    • For high-priority company-wide announcements work with the internal communications team to post the update in #company-fyi and align on a plan to circulate in additional channels like the "While You Were Iterating" Newsletter

---