Skip to content

Update category maturity targets based on capacity

Tim Rizzi requested to merge trizzi-master-patch-75872 into master

Why is this change being made?

The Package stage had some upcoming maturity targets that are not realistic based on our currenty capacity and scheduling. This MR moves the maturity targets for the package registry and helm chart registry back several months. For the package registry, it's due to other SaaS reliability work that we need to address prior to adding more breadth in the form of RubyGems and RPM support. For the Helm chart registry, it's to allow more time for the feature to be adopted and to receive customer feedback.

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.

Merge request reports