Add exit criteria for categories changing from Viable to Complete
Purpose
Today, our process for moving from viable maturity to complete is:
Complete: GitLab the company dogfoods it exclusively. At least 100 customers use it. CM Scorecard score at least 3.63 for the identified JTBDs when tested with external users. Suitable to migrate from existing tools.
This issue suggests adding additional exit criteria for moving to complete, namely:
- Audit events created for the new functionality
- Support for Geo added
- New strings support translation
- Support for GitLab imports
Why is this important?
With every new feature release, we are accumulating debt (translation, geo, compliance) that degrades the experience for our users, especially Enterprise users which must have Geo and Compliance support for any action done in GitLab and for there not to be data loss.
Responsibility
Responsibility of making sure that each new feature/category supports this should be the responsibility of the team that developed it as they are most familiar with this code.
What doesn't this issue cover
Older categories that are beyond complete/lovable