11.2.0-rc2 QA Issue
Release Candidate QA Task
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-08-04 02:00am UTC. After this deadline has passed, Release Managers will proceed with the canary and production deployment.
Merge Requests tested in 11.2.0-rc2
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
Platform ~"Platform"
-
@lbennett | Port CE "Making instance-wide data tools more accessible" Deliverable ~"Platform" frontend -
@lbennett | Resolve "Making instance-wide data tools more accessible" Deliverable ~"In dev" ~"Platform" ~"UX ready" backend ~"convdev" database ~"devops:administration" ~"feature proposal" frontend missed-deliverable -
@fjsanpedro | Fix bug setting http headers in Files API ~"Platform" api backend ~"bug" ~"devops:create" -
@jameslopez | Resolve "GitLab Project Import should use object storage" ~"Cloud Native" Deliverable ~"In dev" Object Storage ~"Platform" backend ~"devops:share" ~"import" ~"project export"
CI/CD ~"CI/CD"
-
@ayufan | Add runner_unsupported
CI failure ~"CI/CD" ~"artifacts" ~"runner" -
@ayufan | EE version of Runner Features ~"CI/CD" ~"artifacts" ~"runner" -
@filipa | Resolve "Link to the runners page should automatically expand the runners settings" ~"CI/CD" frontend
Gitaly ~"Gitaly"
-
@alejandro | Refactor gitlab:import:repos task to remove direct disk access ~"Gitaly" ~"backstage" -
@zj | Remove feature flags from lib/backup ~"Gitaly" ~"backup-restore"
Security Products ~"Security Products"
-
@leipert | Add license management frontend Deliverable ~"Security Products" frontend
frontend
frontend-
@andr3 | EE Port of: Remove fixes for MR refactor regressions from master frontend mr refactor ~"performance" regression -
@andr3 | Remove fixes for MR refactor regressions from master frontend merge requests mr refactor -
@okoghenun | Resolve "List of projects not loading when trying to create an issue from a board (TypeError)" ~"In dev" ~"Plan" ~"Quality:test-gap" frontend issues regression -
@leipert | Backport CSS changes from gitlab-ee!6638 ~"backstage" frontend -
@pslaughter | Add vanilla JS avatar_helper and update existing avatar helpers ~"backstage" frontend -
@leipert | Enable SCSS linting for EE ~"backstage" frontend ~"technical debt" -
@dennis | Resolve "Top nav search bar produces console error when unauthenticated" ~"backstage" ~"bug" frontend -
@iamphill | Fixed Web IDE row dropdowns scrolling list incorrectly ~"Create" frontend ~"web ide"
database
database-
@zj | Add repository languages for projects ~"Manage" database project -
@jacopo-beschi | Resolve "Remove ghost notification settings for groups and projects" ~"Plan" auto updated backend database notifications ~"technical debt" -
@tkuah | Resolve "Chart versions for applications installed by one click install buttons should be version locked" ~"Configuration" Stretch database ~"kubernetes"
uncategorized ~"uncategorized"
-
@dstanley | correct error message on helm tiller installation timeout ~"Configuration" ~"backstage" ~"kubernetes" ~"support-fix" -
@gitlab-crowdin-bot | New Crowdin translations ~"Manage" ~"devops:manage" ~"internationalization" -
@reprazent | Port of EE-translations ~"Manage" ~"backstage" ~"devops:manage" ~"internationalization" -
@zj | Add repository languages for projects ~"Manage" project -
@annabeldunstone | Fix scss-lint error ~"backstage" -
@jprovaznik | Ignore sorting parameter when exporting issues to CSV ~"Plan" backend -
@oswaldo | Filter diff files by given path on DB instead Ruby ~"Plan" backend merge requests ~"performance" -
@jameslopez | Update GITLAB_SHELL_VERSION to 8.1.0 ~"backstage" -
@tkuah | Use Helm 2.7.2 for GitLab Managed Apps ~"Configuration" Stretch ~"auto devops" ~"kubernetes" -
@leipert | Get rid of unnecessary commit action in pipelines controller ~"backstage" ~"technical debt" -
@reprazent | Fix deploy tokens without expire_at
crashes Next Patch Release ~"bug" regression regression:11.2 -
@stanhu | Fix failing 500 errors when deploy tokens are used to clone
Automated QA for 11.2.0-rc2
If the last Daily staging QA
pipeline was run for 11.2.0-rc2,
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/-/jobs/86690544 =>
- Fork is failing which is expected since sign-ups are disabled on staging: gitlab-org/quality/staging#2 (closed)
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