Update Manage category Maturity July 2021

Why is this change being made?

Related to Product#2840 (comment 649847126)

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.

---

assigned to @ogolowinski

changed the description

added 1 commit

• c9197a47 - Apply 1 suggestion(s) to 1 file(s)

Compare with previous version

added 1 commit

• 1eee168a - Update data/categories.yml

Compare with previous version

changed title from Update Manage category Maturity to Update Manage category Maturity July 2021

mentioned in issue #12126 (closed)

added 1 commit

• a899602c - Apply 1 suggestion(s) to 1 file(s)

Compare with previous version

added 1 commit

• bdb275c2 - Update data/categories.yml

Compare with previous version

added 1 commit

• ed9637b8 - Update data/categories.yml

Compare with previous version

resolved all threads

started a merge train

removed this merge request from the merge train because Reference not found

started a merge train

merged

mentioned in commit 3588240c