11.3.0-rc4 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-09-07 07:30 UTC. After this deadline has passed, Release Managers will proceed with the canary and production deployment.
Merge Requests tested in 11.3.0-rc4
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"
-
@smcgivern | Resolve "Postgres timeout when counting number of CI builds for usage ping" ~"Plan" admin dashboard backend ~"bug" reproduced on GitLab.com ~"usage ping" -
@smcgivern | Resolve "Postgres timeout when counting number of CI builds for usage ping" ~"Plan" backend ~"usage ping" -
@digitalmoksha | Enable CommonMark for files and wikis ~"Plan" markdown release post item
Create ~"Create"
-
@DouweM | Resolve "Return how many commits the source branch is behind the target branch through the API" ~"Community Contribution" ~"Create" api customer merge requests -
@pslaughter | EE Port (Resolve "UI: Move "default branch" setting under "repository" settings") ~"Create" Deliverable UI polish ~"UX ready" auto updated ~"devops:create" ~"feature proposal" frontend repository settings -
@dzaporozhets | Filter web hooks by branch ~"Community Contribution" ~"Create" release post item repository -
@smcgivern | Reduce queries for CI artifacts from MR widget ~"Create" ~"Secure" backend merge requests ~"performance" -
@oswaldo | Allow MR authors to approve their MRs ~"Create" approvals backend ~"performance" -
@stanhu | Bump browser gem to v2.5.3 ~"Create" backend ~"dependency update" -
@nick.thomas | CE backport of changes that introduce custom instance-level templates to EE ~"Create" -
@nick.thomas | Expand instance-level templates to cover .gitlab-ci.yml, .gitignore and Dockerfile ~"Create" ~"devops:create" -
@iamphill | Upgraded Monaco editor version ~"Create" ~"backstage" ~"dependency update" frontend ~"web ide" -
@reprazent | Extract code owners from a CODEOWNERS file ~"Create" ~"devops:create" -
@jameslopez | Add git_v2 flag to GitalyClient ~"Create" ~"Gitaly" -
@rymai | Recognize 'UNLICENSE' license files ~"Community Contribution" ~"Create"
Manage ~"Manage"
-
@dennis | Resolve "Improve project overview UI" Deliverable ~"Manage" ~"UX ready" ~"devops:manage" direction ~"feature proposal" frontend release post item -
@wortschi | Resolve "Update presentation for SSO providers on log in page" Deliverable GitLab.com Priority ~"Manage" ~"UX ready" authentication ~"devops:manage" frontend gitlab.com oauth ~"ready for review" -
@ash.mckenzie | Custom Action support ~"Geo" ~"Manage" authentication auto updated backend repository -
@lbennett | Resolve "Remove usage ping payload from Cohorts, add to Settings" Deliverable ~"Manage" analytics ~"devops:manage" frontend ~"usage ping"
CI/CD ~"CI/CD"
-
@grzesiek | Add support for advanced CI/CD config extension / EE ~"CI/CD" ~"devops:verify" -
@grzesiek | Add support for advanced CI/CD config extension with extends:~"CI/CD" Deliverable ~"devops:verify" -
@rymai | Explicit hashed path check for trace, prevents background migration from… ~"CI/CD" ~"Community Contribution" ~"backstage" -
@SteveAzz | Add terminal path to job API response ~"CI/CD" Deliverable ~"backstage" ~"devops:verify"
Packaging ~"Packaging"
-
@dzaporozhets | Add CI Job token support to Maven packages API ~"Packaging" ~"packaging"
Monitoring ~"Monitoring"
-
@lulalala | Ignore irrelevant sql commands in metrics ~"Monitoring" ~"application performance monitoring" backend database
Secure ~"Secure"
-
@leipert | Add missing paths to EE environment serializer Deliverable GitLab Ultimate ~"Secure" backend ~"devops:secure"
frontend frontend
-
@kushalpandya | Make MR diff file filter input Clear button functional ~"bug" ~"devops:create" frontend merge requests
database database
-
@tkuah | Enable Kubernetes RBAC for GitLab Managed Apps for existing clusters ~"Configure" Deliverable ~"auto devops" customer database deploy ~"devops:configure" direction ~"feature proposal" idea-to-production ~"kubernetes" missed-deliverable ~"services" -
@tkuah | EE port for 29398 support kubernetes rbac for gitlab managed apps ~"Configure" Deliverable database ~"kubernetes"
uncategorized ~"uncategorized"
-
@dzaporozhets | Remove unnecessary logic from group labels page ~"backstage" -
@dzaporozhets | Remove unnecessary logic from group labels page ~"backstage" -
@andrewn | Fix multipart error on rails reload ~"backstage" ~"bug" -
@dbalexandre | Fix app/views/projects/settings/repository/show.html.haml ~"backstage" -
@andrewn | Add route information to lograge structured logging for API logs Observability ~"backstage" ~"logging" production request -
@dennis | port "Improve project overview UI" to EE auto updated -
@stanhu | Add User-Agent to production_json.log production request security -
@reprazent | Port changes for CODEOWNERS to CE ~"backstage" -
@stanhu | Fix attachments not displaying inline with Google Cloud Storage Object Storage
Automated QA for 11.3.0-rc4
If the last Daily staging QA pipeline was run for 11.3.0-rc4,
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
Edited by Nick Thomas