11.7.0-rc5 QA Issue
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 working hours after the deploy to staging completes.
- The deadline to which subsequent release candidates moves on from staging environment is 12 working 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 2019-01-12 00:58 UTC. After this deadline has passed, Release Managers will proceed with the canary and production deployment.
Merge Requests tested in 11.7.0-rc5
Example:
@Engineer1
| Apply notification settings level of bacons to all child bacons ~Plan ~groups subgroups@Engineer2
| Resolve "Timeout searching group bacons" ~Plan backend ~bug database ~groups issues ~performance@Engineer3
| Nonnegative meatball weights in issuable sidebar short ribs Deliverable ~Plan backend direction frontend issues
- Found problem, does not work because... LINK_ISSUE_HERE
@Engineer4
| Moving rev-list pastrami bacons to Lfs Prosciutto ~Create backend ~lfs
Create ~"Create"
-
@annabeldunstone | Add syntax highlighting to suggestion diff ~"Create" ~"Pick into 11.6" frontend -
@sbigelow | Resolve "Inconsistent spacing between note and user avatar in discussions" ~"Create" ~"bug" frontend regression regression:11.7 -
@stanhu | Fix broken templated "Too many changes to show" text ~"Create" ~"Pick into 11.6"
Verify ~"Verify"
-
@stanhu | Fix Error 500 when deleting a pipeline via the API ~"Pick into 11.6" ~"Verify" ~"bug" regression:11.6
Release ~"Release"
-
@shampton | Resolve "Feature Flags - Table View filter tabs" Deliverable GitLab Premium ~"Release" ~"UX ready" ~"devops:release" feature flag ~"feature flags" feature management frontend missed:11.6 missed:11.7
Monitoring ~"Monitoring"
-
@tristan.read | Update tracing settings to match error tracking ~"Monitoring" ~"bug" ~"devops:monitor" direction feature flag frontend regression
Secure ~"Secure"
-
@gonzoyumo | Backport container scanning fixtures ~"Secure" backend ~"backstage" ~"container scanning" ~"devops:secure" -
@gonzoyumo | Fix container scanning parser ~"P1" ~"S1" ~"Secure" ~"backstage" ~"bug" ~"container scanning" ~"devops:secure" feature flag
database
databaseAutomated QA for 11.7.0-rc5
If the last Daily staging QA
pipeline was run for 11.7.0-rc5,
you can just report the result in this issue.
Otherwise, start a new Daily staging QA
pipeline by clicking the
"Play" button and wait for the pipeline to finish.
Post the result of the test run here.
If there are errors, create a new issue for each failing job (you can
use the "New issue" button from the job page itself), in the
https://gitlab.com/gitlab-org/quality/staging project and mention
the @gl-quality
group.
/cc @gl-quality