Uploaded image for project: 'MicroShift'
  1. MicroShift
  2. USHIFT-6052

[QE] Errata release lead (sprint 276)

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Done
    • Icon: Normal Normal
    • None
    • None
    • QE
    • None
    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • 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:

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

       

       

              knarra@redhat.com Rama Kasturi Narra
              knarra@redhat.com Rama Kasturi Narra
              None
              None
              None
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: