Skip to content

11.9.0-rc1 QA Issue

Process

Each engineer validates and checks off each of their assigned QA task(s).

  1. 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.
  2. 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.
  3. 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

QA testing on staging.gitlab.com for this issue should be completed by 2019-03-06 11:27 UTC. After this deadline has passed, Release Managers will proceed with the canary and production deployment.

Merge Requests tested in 11.9.0-rc2

Community contribution Community contribution

Plan ~"Plan"

Create ~"Create"

Manage ~"Manage"

Verify ~"Verify"

Release ~"Release"

Geo ~"Geo"

Gitaly ~"Gitaly"

Package ~"Package"

Configure ~"Configure"

Monitor ~"Monitor"

Secure ~"Secure"

frontend frontend

database database

uncategorized ~"uncategorized"

Automated QA for 11.9.0-rc2

If the last Daily staging QA pipeline was run for 11.9.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.

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 Brett Walker