11.6.0-rc5 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-12-12 07:45 UTC. After this deadline has passed, Release Managers will proceed with the canary and production deployment.
Merge Requests tested in 11.6.0-rc5
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-
@mikegreiling | Dropdown: Make Identicons of a subgroup in the breadcrumb dropdown not take a whole line 1st contribution Community contribution Hackathon frontend -
@iamphill | Show primary button when all labels are prioritized Community contribution ~"Plan" UX frontend -
@dzaporozhets | Ability to override Issuer Email for Cert Manager Community contribution -
@DouweM | Changed frontmatter filtering to support YAML, JSON, TOML, and arbitrary languages Community contribution ~"Create" ~"devops:create" ~"feature proposal" markdown
Plan ~"Plan"
-
@winh | Pass commit when posting diff discussions ~"Plan" ~"devops:create" diff frontend merge requests -
@smcgivern | Add a flag to use a subquery for group issues search ~"Plan" backend ~"bug" feature flag issues ~"performance" -
@jprovaznik | [EE] Use FastDestroy for deleting uploads Object Storage ~"Plan" backend -
@jprovaznik | Use FastDestroy for deleting uploads Object Storage ~"Plan" backend feature flag -
@winh | Fix duplicate boardsStore variable in milestone select ~"Plan" boards ~"bug" ~"devops:plan" frontend milestones regression regression:11.5 -
@engwan | Show closed epics in roadmap ~"Plan" ~"UX ready" backend epics frontend ~"portfolio management" roadmaps -
@felipe_artur | Add milestones autocomplete for epics ~"Plan" backend epics milestones ~"ready for review" -
@felipe_artur | [CE] - Add milestones autocomplete for epics ~"Plan" backend epics milestones -
@kushalpandya | Epic issue list and related issue list re-design ~"Plan" direction epics issues ~"portfolio management" ~"ready for review"
Create ~"Create"
-
@oswaldo | Remove un-used data from discussions endpoint ~"Create" backend ~"feature proposal" ~"performance" -
@stanhu | Truncate merge request titles with periods instead of ellipsis ~"Create" ~"bug" customer -
@nick.thomas | Fix transaction pollution in Shard.by_name ~"Create" ~"backstage" -
@nick.thomas | Fix transaction pollution in Shard.by_name (EE) ~"Create" ~"backstage" -
@nick.thomas | Improve error message when attempting to reopen MR and there's a new open MR for the same branch ~"Create" ~"P3" ~"S3" backend ~"bug" customer merge requests -
@lulalala | Update merge request's merge_commit after branch update ~"Accepting merge requests" ~"Create" Deliverable ~"In dev" ~"P3" ~"S3" backend ~"bug" ~"devops" feature flag merge requests -
@DouweM | [EE] Remove RemoveOldWebHookLogsWorker ~"Create" backend ~"backstage" -
@pslaughter | Web Terminal FE ~"Create" Deliverable GitLab Ultimate ~"P1" ~"UX ready" ~"devops:create" direction ~"feature proposal" frontend missed-deliverable missed:11.4 missed:11.5 ~"web ide" -
@tiagonbotelho | Backports changes made to One notification per code review ~"Create" Deliverable emails ~"feature proposal" merge requests -
@reprazent | Reenable CODEOWNERS ~"Create" ~"backstage" ~"devops:create" -
@toon | Fill project_repositories for hashed storage projects ~"Create" Deliverable ~"Geo" Geo Administration backend ~"backstage" database ~"devops:create" production request -
@andr3 | Port to EE: Resolve "Navigating unresolved discussions on Merge Request page" ~"Create" Deliverable ~"P1" ~"S2" ~"bug" ~"devops" frontend merge requests regression
Manage ~"Manage"
-
@wortschi | Resolve "Add subscription table to GitLab.com billing areas" Deliverable ~"Manage" ~"P1" database ~"devops:manage" frontend gitlab.com -
@rdavila | Backports some changes from gitlab-ee!7885 ~"Manage" backend -
@dennis | Port "Further improvements to Project overview UI" to EE Deliverable ~"Manage" auto updated frontend project -
@dennis | Resolve "Further improvements to Project overview UI" Deliverable ~"Manage" ~"P2" UX ~"devops:manage" direction frontend project -
@jamedjo | Group SAML SSO page warns when linking account ~"Manage" backend ~"enhancement" gitlab.com saml
Verify ~"Verify"
-
@dosuken123 | Fix broken seeder 11.6 ~"Configure" ~"Verify" ~"backstage" ~"bug" -
@grzesiek | Encrypt CI/CD builds tokens Deliverable ~"Verify" database security -
@tmaczukin | Update gitlab runner helm chart to 0.1.39 ~"Verify" ~"dependency update" ~"devops:configure" ~"devops:verify" -
@grzesiek | Encrypt CI/CD builds tokens / EE ~"Verify" reverted security -
@grzesiek | Add CI/CD build encrypted tokens (after revert) ~"Verify" reverted security
Geo ~"Geo"
Gitaly ~"Gitaly"
-
@zj | Allow public forks to be deduplicated ~"Gitaly" database -
@zj | Allow public forks to be deduplicated ~"Gitaly" database ~"feature proposal"
Packaging ~"Packaging"
-
@dzaporozhets | Revert "Add instance-level maven endpoint for download" ~"Packaging" ~"devops:package" ~"packaging"
Monitoring ~"Monitoring"
-
@adrielsantiago | Port "Utilize new charting library for metrics dashboard" to EE Charts ~"Monitoring" frontend
Secure ~"Secure"
-
@samdbeckham | Resolve "Group Security Dashboard metrics MVC" Deliverable GitLab Ultimate ~"In dev" ~"Secure" ~"UX ready" backend ~"devops:secure" direction ~"feature proposal" frontend release post item security dashboard -
@gonzoyumo | Add package name to dependency scanning reports ~"In dev" ~"Secure" Stretch backend ~"backstage" ~"dependency scanning" ~"devops:secure" ~"technical debt" -
@gonzoyumo | Add feature flag for Dependency Scanning reports parsing ~"Secure" ~"backstage" ~"devops:secure"
frontend
frontend-
@kushalpandya | CE Backport: Fix labels tooltip in collapsed Epics sidebar ~"backstage" ~"bug" frontend -
@pslaughter | CE Port of "Web Terminal FE" ~"backstage" frontend ~"web ide" -
@ClemMakesApps | Integrate csslab (EE) Deliverable frontend
uncategorized ~"uncategorized"
-
@at.ramya | Qa remove spec from smoke tests. -
@ayufan | Log and pass correlation-id between Unicorn, Sidekiq and Gitaly ~"backstage" ~"logging" -
@timzallmann | EE Compat Version for Resolve "Extended User Centric Tooltips" -
@tatkins | Change link for upgrades and renewals questions auto updated
Automated QA for 11.6.0-rc5
If the last Daily staging QA
pipeline was run for 11.6.0-rc5,
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