Skip to content

Adjusted configure maturity dates

Viktor Nagy (GitLab) requested to merge nagyv-gitlab-master-patch-56170 into master

Why is this change being made?

  • The IaC maturity scorecard is almost finished. Future IaC dates are set based on the assumption that additional investment will allow for a dedicated team. (Related to Monthly category dates review : September (Product#4881 - closed))
  • We are currently working on shared items for Kubernetes and Deployment Management
    • Once basic observability and Helm support is available, I test if our users consider it Complete
    • Adding basic observability and Helm support will likely be available in FY24Q1
  • We want to continue with working on Deployment Management
    • As we had a small team until recently, we delivered on Deployment Management slower than initially planned.
    • The team is filled and we hope to speed up delivery soon.
    • We are still in the planning phase of our complete solution. For these reasons, I plan to deliver a Complete solution by the end of 2024.
  • Once Deployment Management is Complete, we can update Auto DevOps to use the Deployment Management features and turn it into Complete as well
    • The Auto DevOps date is very risky, this is my best bet given our current knowledge.

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 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 Viktor Nagy (GitLab)

Merge request reports