11.1.0-rc13 QA Issue
Release Candidate QA Task
Process
A Release manager with the help of a Quality engineer will populate the Merge Requests tested section. The information is taken from our Automated QA task generation script. The documentation can be found at: https://gitlab.com/gitlab-org/release/docs/blob/master/general/qa-issue-generation.md
Each engineer then validates and checks off each of their assigned QA task(s).
- Check off each Merge Request changes that you've tested successfully and note any issues you've created and check them off as they are resolved.
- If a problem is found:
- Create an issue for it and add a sub bullet item under the corresponding validation checklist task. Link the issue there.
- Add the severity label
- Raise the problem in the discussion and tag relevant Engineering and Product managers.
- If a regression is found:
- Create an issue for it
- Add the severity label and the regression label
- Raise the regression in the discussion and tag relevant Engineering and Product managers.
General Quality info can be found in the Quality Handbook.
Deadline
- The deadline to which the first release candidate (RC1) moves on from staging environment is 24 hours after the deploy to staging completes.
- The deadline to which subsequent release candidates moves on from staging environment is 12 hours after the deploy to staging completes.
Note: For Release Managers, for each release candidate, update the time here to reflect the latest release candidate deploy.
QA testing on staging.gitlab.com should be completed by 09:00 UTC, Wed 18th. After this deadline has passed, Release Managers will proceed with the canary and production deployment.
Merge Requests tested in RC 11.1.0-rc13
Example:
@Engineer1
| Apply notification settings level of bacons to all child bacons ~Discussion ~groups subgroups@Engineer2
| Resolve "Timeout searching group bacons" ~Discussion backend ~bug database ~groups issues ~performance@Engineer3
| Nonnegative meatball weights in issuable sidebar short ribs Deliverable ~Discussion backend direction frontend issues
- Found problem, does not work because... LINK_ISSUE_HERE
@Engineer4
| Moving rev-list pastrami bacons to Lfs Prosciutto ~Platform backend ~lfs
Discussion ~"Discussion"
-
@mdelaossa | Resolve "NoMethodError: undefined method `namespace' for nil:NilClass" ~"Discussion" backend ~"bug" merge requests regression -
@ClemMakesApps | Resolve "Pipeline graph in new merge request widget is flickering" ~"Discussion" ~"bug" frontend merge requests regression reproduced on GitLab.com
Geo ~"Geo"
-
@mkozono | Geo: Fix repository updated replication race condition ~"Geo" ~"Geo DR" ~"bug" data integrity
Monitoring ~"Monitoring"
-
@jivanvl | Resolve "Metrics drop down doesn't show all environment, some not clickable" ~"Monitoring" ~"backstage" ~"bug"
frontend
frontend-
@timzallmann | Resolve "MR: Reduce the memory footprint of the component tree" ~"backstage" frontend merge requests mr refactor ~"performance" regression
uncategorized ~"uncategorized"
-
@dennis | Resolve "Disable GCP free credit banner at instance level" ~"Accepting Merge Requests" ~"Configuration" ~"UX ready" admin dashboard ~"feature proposal" infrastructure configuration ~"kubernetes" settings -
@stanhu | Fix undefined constant Gitlab::Git::HooksService::PreReceiveError ~"bug" ~"mirror" regression -
@dennis | port 48578-disable-gcp-free-credit-banner-at-instance-level to EE ~"Configuration" admin dashboard ~"kubernetes" settings
Automated QA for 11.1.0-rc13
Cross-post from https://dev.gitlab.org/gitlab-com/migration/issues/35#note_129331:
Scheduled pipeline did test 11.1.0-rc13-ee this morning and everything passed: https://gitlab.com/gitlab-org/quality/staging/-/jobs/82507817
🎉
If there are errors, create an "Automation Triage" issue, name it Automation Triage RELEASE_MAJOR_VERSION RC#
and link it to this issue.
In the triage issue include all the detailed test logs and screenshots.
/cc @gl-quality