Score Q1 edge/quality team OKRs
Scoring the previous quarter OKRs for Edge/Quality.
Please correct me if I am mistaken on any of this progress. Here is my rationale.
- Quality: Complete the work to make GitLab QA production-ready => 100%
- Quality: Define the architecture of and produce an end-to-end prototype for a self-service metrics generator => 5%
- Discussion is just starting off with Mark's protype still needs review from the team.
- Quality: Define and schedule high-value issues for improving the staging test environment => 0%
- I did not see any MRs linked to this issue hence assuming no progress on this. I see discussions but hesitant to score any tangible progress against this.
- Quality: Write 2 GitLab QA tests related to creating and managing Issues => 50%
- I see one MR for creating hence 50% => nice!
- Quality: Write 2 GitLab QA tests related to CI/CD => 100%
- I see the two MRs linked closed, hence done.
- Edge: Work with backend teams to move 100% of EE-specific files and 50% of EE-specific lines of code to the top-level
/eedirectory => 50%- This is based on my gut feeling on the team discussions in https://gitlab.com/gitlab-org/quality/team-tasks/issues/1
- Edge: Investigate how to extract EE-specific files/lines of code for JavaScript, CSS, and Grape API => 25%
- We should group this into the above effort and have a single point to track. Scoring on the status of the frontend only.
- Edge: Reduce average CE pipeline duration to 30 minutes => 70%
- Saw 2/3 done hence 70%
- Edge: Solve at least 1 outstanding performance issues => 100%
- I am not sure which MR we did for this, assuming this is low hanging fruit hence done?
cc/ @bjgopinath @rymai
Edited by Mek Stittri