11.5.0-rc8 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 2018-11-14 23:10 UTC. After this deadline has passed, Release Managers will proceed with the canary and production deployment.
Merge Requests tested in 11.5.0-rc8
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
Community contribution
Community contribution-
@smcgivern | Change issues analytics breadcrumb Community contribution ~"Plan" ~"bug" frontend
Create ~"Create"
-
@nick.thomas | Fix a race condition in the shard population logic ~"Create" ~"P3" ~"S3" regression regression:11.5 -
@iamphill | Fixed image commenting on moved files ~"Create" frontend merge requests -
@DouweM | Disable CODEOWNERS for the time being ~"Create" ~"backstage"
Verify ~"Verify"
-
@filipa | Adds back missing CI favicon ~"Verify" ~"bug" frontend regression regression:11.5
Monitoring ~"Monitoring"
-
@psimyn | Resolve "Tracing empty empty state image fails to load" ~"Monitoring" Next Patch Release ~"bug" ~"devops:monitor" -
@splattael | Resolve "Ops Dashboard should be available for public projects on GitLab.com" ~"Monitoring" Next Patch Release ~"bug" ~"devops:monitor" ~"feature proposal" regression regression:11.5
Secure ~"Secure"
-
@plafoucriere | Set an empty entrypoint for license_management job ~"Secure" ~"backstage" ~"bug" ~"devops:secure" -
@samdbeckham | Resolve "View issue button doesn't work in dashboard modal" ~"Secure" ~"bug" ~"devops:secure" frontend regression:11.5
frontend
frontend-
@fatihacet | Border radius fixes for redesigned discussions frontend -
@annabeldunstone | Align all avatars and system notes in discussion UI polish frontend -
@annabeldunstone | Fix broken UI on commit discussions ~"P2" ~"S2" frontend regression:11.5 -
@fatihacet | Update draft comments design to match new design frontend
uncategorized ~"uncategorized"
Automated QA for 11.5.0-rc8
If the last Daily staging QA
pipeline was run for 11.5.0-rc8,
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