11.7.0-rc3 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-09 16:29 UTC. After this deadline has passed, Release Managers will proceed with the canary and production deployment.
Merge Requests tested in 11.7.0-rc3
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-
@fatihacet | Externalize strings from /app/views/shared/notes
Community contribution frontend ~"internationalization" -
@fatihacet | Externalize strings from /app/views/shared/notes
Community contribution frontend ~"internationalization"
Plan ~"Plan"
-
@jarka | Fix adding labels to epics using quick actions ~"P3" ~"Plan" ~"S3" backend ~"bug" ~"devops:plan" epics ~"portfolio management" quick actions reproduced on GitLab.com -
@winh | Add search field to issue board switcher Deliverable GitLab Starter ~"Plan" boards ~"devops:plan" direction ~"feature proposal" frontend -
@engwan | Add autocomplete for issues and MRs in epics ~"Accepting merge requests" ~"Create" ~"Plan" ~"UX ready" backend direction epics frontend issues merge requests ~"portfolio management" -
@mdelaossa | Fix EpicBaseEntity human_readable_timestamp ~"P2" ~"Plan" ~"S2" api backend ~"bug"
Create ~"Create"
-
@lulalala | Add ApprovalRule model ~"Create" Deliverable GitLab Premium ~"P1" approvals backend ~"backstage" database ~"devops:create" direction merge requests -
@dbalexandre | Fix MR sidebar to correctly warning if assignee can't merge ~"Create" ~"P2" ~"S2" regression regression:11.7 -
@stanhu | Revert "Merge branch '3062-improve-project-cache' into 'master'" ~"Create"
Manage ~"Manage"
-
@rdavila | BUGFIX: admins were unable to change the GL.com plan for a namespace ~"Manage" backend ~"backstage" ~"bug" regression:11.7
Release ~"Release"
-
@dosuken123 | Add summary entity to FeatureFlagController#index
endpoint Deliverable GitLab Premium ~"Release" ~"UX ready" ~"backstage" ~"devops:release" ~"feature flags" feature management frontend missed-deliverable missed:11.6 -
@filipa | Fixes missing margin in releases block ~"Release" ~"backstage" ~"bug" frontend regression
Geo ~"Geo"
-
@brodock | Hashed Storage: Only set as read_only
when starting the per-project migration Deliverable ~"Geo" Geo Administration database
Monitoring ~"Monitoring"
-
@rpereira2 | Add table and model for error tracking settings Deliverable ~"Monitoring" database ~"devops:monitor" direction feature flag ~"feature proposal" release post item -
@tristan.read | Resolve "Sentry Configuration" Deliverable ~"Monitoring" ~"devops:monitor" direction feature flag ~"feature proposal" frontend release post item
Secure ~"Secure"
-
@samdbeckham | Allows the GSD to select multiple filters Deliverable GitLab Ultimate ~"In dev" ~"Secure" ~"UX ready" backend ~"devops:secure" direction ~"feature proposal" frontend release post item security dashboard -
@gonzoyumo | Add permissions check when creating an issue from a vulnerability Deliverable ~"P2" ~"S2" ~"Secure" backend ~"bug" ~"devops:secure" -
@samdbeckham | Adds project filtering to the GSD Deliverable GitLab Ultimate ~"In dev" ~"Secure" ~"UX ready" backend ~"devops:secure" direction ~"feature proposal" frontend release post item security dashboard -
@groulot | Store container scanning results in the database GitLab Ultimate ~"Secure" backend ~"container scanning" database ~"devops:secure" -
@groulot | Use Container Scaning report fixture from EE ~"Secure" backend ~"backstage" ~"container scanning" ~"devops:secure" -
@gonzoyumo | Add feature flag for container scanning parsing ~"Secure" ~"backstage" ~"container scanning" ~"devops:secure"
frontend
frontend-
@adrielsantiago | Add threshold lines in metrics graph Charts Deliverable direction feature flag frontend release post item -
@engwan | CE backport of gitlab-ee!8936 ~"backstage" frontend
uncategorized ~"uncategorized"
-
@jarka | CE port: Use parent instead of project for quick actions backend ~"backstage" quick actions -
@stanhu | Pseudonymizer: Gracefully handle empty pseudo entries Meltano
Automated QA for 11.7.0-rc3
If the last Daily staging QA
pipeline was run for 11.7.0-rc3,
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