-
Task
-
Resolution: Done
-
Normal
-
None
-
None
-
None
-
Quality / Stability / Reliability
-
False
-
-
False
-
2
-
None
-
None
-
uShift Sprint 276
Monitor OCP advisories each week and determine if MicroShift advisories are also required.
The process is documented in this Confluence page: https://spaces.redhat.com/pages/viewpage.action?spaceKey=PLUG&title=USHIFT+Publishing+Errata
The process consists of 2 steps:
- Duplicate USHIFT-5382 [QE] 4.Y.Z MicroShift errata publication check every time a new OCP release is available (you can view them in this calendar)
- For every release, if a MicroShift advisory is created, create "[QE] 4.Y.Z errata release testing [<RELEASE_DATE>]" ticket to track testing (see template tickets for both of these).
A small script called advisory_publication.sh can simplify the work needed to determine if a ticket needs to be created.
To use:
./advisory_publication_report.sh <errata release version>
- clones
-
USHIFT-5813 [QE] Errata release lead (sprint 272)
-
- Closed
-
- is cloned by
-
USHIFT-6097 [QE] Errata release lead (sprint 277)
-
- Closed
-