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
2. On Friday at the end of the day, check if new version should be requested it by looking in the smartsheet calendar:
   1. The versions to check are going to be in Fast Channel during next week. For every version check:

1. 1. 1. if there are CVEs: running the advisory_publication_report.sh script
      2. if 90 days mark check: check for the published erratas and date
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).

Resources
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>