11.5.0-rc7 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 03:04 UTC. After this deadline has passed, Release Managers will proceed with the canary and production deployment.
Merge Requests tested in 11.5.0-rc7
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
Create ~"Create"
-
@stanhu | Fix MergeRequestService erroring out on deleted branch ~"Create" ~"backstage" regression:11.5
Verify ~"Verify"
-
@ayufan | Fix tags for environments ~"P1" ~"S1" ~"Verify" ~"bug" ~"devops:verify" pipeline regression:11.5 ~"runner"
Release ~"Release"
-
@SteveAzz | Prepare 11.5 RC4 release ~"Release" -
@SteveAzz | Prepare 11.5 RC5 release ~"Release" -
@SteveAzz | Prepare 11.5 RC5 EE release ~"Release" -
@cpallares | Prepare 11.5 RC6 EE release ~"Release" -
@cpallares | Prepare 11.5 RC6 release ~"Release" -
@SteveAzz | Prepare 11.5 RC7 EE release ~"Release"
Configure ~"Configure"
-
@DylanGriffith | Fix error handling bugs in kubernetes integration ~"Configure" ~"bug" -
@tkuah | Fix deployment jobs using nil token ~"Configure" ~"P1" ~"S1" ~"bug" ~"kubernetes" regression regression:11.5
Secure ~"Secure"
-
@ayufan | backport: Always proxy reports downloads ~"Secure" ~"bug" ~"devops:secure" regression -
@samdbeckham | Resolve "Vulnerability modal discrepancies on Group Security Dashboard" ~"Secure" ~"bug" ~"devops:secure" frontend regression regression:11.5 security dashboard
frontend
frontend-
@iamphill | Stop multiple discussion requests frontend merge requests regression regression:11.5 -
@annabeldunstone | Fix alignment of diff comment buttons frontend merge requests regression:11.5
Automated QA for 11.5.0-rc7
If the last Daily staging QA
pipeline was run for 11.5.0-rc7,
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.
https://gitlab.com/gitlab-org/quality/staging/pipelines/36444677
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