Increase clarity for Reliability's involvement in Readiness
Development teams for the most part are using https://docs.gitlab.com/ee/policy/experiment-beta-support.html as their guide for what is necessary for the requirement for different features. The readiness review process is described here: https://about.gitlab.com/handbook/engineering/infrastructure/production/readiness/ and the template for reviews is here: https://gitlab.com/gitlab-com/gl-infra/readiness/blob/master/.gitlab/issue_templates/production_readiness.md#readiness-mr-template
Infrastructure recently created a helpful guide https://about.gitlab.com/handbook/engineering/infrastructure/feature-support.html for establishing criteria for Reliabilty support.
This issue is to address some shortcomings in making sure it is clear to development teams what is expected when a Readiness review is opened, and what the criteria for different stages of feature maturity:
-
Schedule a meeting with @rnienaber to discuss this issue: Meeting scheduled for Aug 7th since Rachel on PTO notes -
Create MRs against the current readiness template, using suggestions in Rachel's doc - Updates the Readiness Review Infra page (gitlab-com/www-gitlab-com!128217 - merged)
- Updates the readiness template (readiness!176 - merged)
- Adds references to the new Readiness Review pro... (gitlab-org/gitlab!129773 - merged)
- Updates the Readiness Review Infra page (gitlab-com/www-gitlab-com!128217 - merged)
-
Reach out to stakeholders for sync feedback: -
Followup with Rachel -
Delivery (pinged Michele about this) (notes) -
Infrasec Met with Paulo https://docs.google.com/document/d/1wjWoF7Q2UFYhZoscA3dvQ86W0yLz_ogD0R_-ED1C6jA/edit readiness!181 (merged) -
Another staff engineer in Reliability (Igor) (notes) -
Another manager in Reliability (Kenn notes) (Anthony notes)
-