11.4.0-rc6 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 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 2018-10-16 12:39 UTC. After this deadline has passed, Release Managers will proceed with the canary and production deployment.
Merge Requests tested in 11.4.0-rc6
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
Plan ~"Plan"
-
@andr3 | Resolves "Reviews: Resolving or unresolving discussions with “Add comment now” does not work" ~"Create" ~"Plan" ~"bug" ~"code review" merge requests regression regression:11.4 -
@lulalala | Update previous epic milestone dates when issue switches epic ~"P2" ~"Plan" ~"S2" ~"bug" ~"portfolio management" regression:11.3
Create ~"Create"
-
@andr3 | Resolve "Make file browser hidden by default for mobile screens" and improve layout in small screens too ~"Create" ~"UX ready" ~"bug" ~"devops:create" frontend merge requests regression regression:11.4
CI/CD ~"CI/CD"
-
@filipa | Updates the check for started in job header ~"CI/CD" ~"bug" regression regression:11.4 -
@SteveAzz | Add stage name in job.json response ~"CI/CD" ~"bug" ~"devops:verify" regression regression:11.4 reproduced on GitLab.com -
@filipa | Hide job sidebar on mobile ~"CI/CD" frontend regression regression:11.4
frontend
frontend-
@andr3 | Backport CE changes for: Resolves "Reviews: Resolving or unresolving discussions with “Add comment now” does not work" ~"backstage" frontend
Automated QA for 11.4.0-rc6
If the last Daily staging QA
pipeline was run for 11.4.0-rc6,
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.
QA is
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