11.5.0-rc9 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-15 19:56 UTC. After this deadline has passed, Release Managers will proceed with the canary and production deployment.
Merge Requests tested in 11.5.0-rc9
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
Plan ~"Plan"
-
@engwan | Disable updating appearance of filter tokens for special values ~"Plan" frontend issues merge requests regression regression:11.5
Create ~"Create"
-
@oswaldo | Comment on any expanded diff line on MRs (with feature-flag) ~"Create" backend diff feature flag ~"feature proposal" merge requests -
@oswaldo | [EE] Comment on any expanded diff line on MRs (with feature-flag) ~"Create" backend diff feature flag ~"feature proposal" merge requests
Manage ~"Manage"
-
@wortschi | Resolve "Activity Feed - Missing padding in event note when a branch is deleted" ~"In review" ~"Manage" ~"bug" frontend regression regression:11.5
Release ~"Release"
-
@jarv | Prepare 11.5 RC9 EE release ~"Release"
frontend
frontend-
@annabeldunstone | Add white background to commit diff comments frontend -
@annabeldunstone | Fix vertical line alignment in discussion & diff border-radius frontend -
@annabeldunstone | Fix styling of snippet and commit discussion comments frontend regression:11.5 ~"technical debt"
uncategorized ~"uncategorized"
-
@cpallares | Prepare 11.5 RC8 release ~"Delivery" -
@DouweM | Fix bug causing not all emails to show up in commit email selectbox
Automated QA for 11.5.0-rc9
If the last Daily staging QA
pipeline was run for 11.5.0-rc9,
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