Uploaded image for project: 'Red Hat OpenStack Services on OpenShift'
  1. Red Hat OpenStack Services on OpenShift
  2. OSPRH-20696

Improve efficiency for z-stream releases

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • None
    • 5
    • False
    • Hide

      None

      Show
      None
    • False
    • Not Selected

      Goal: 

      • Our team is getting more comfortable with the time-based release cadence, and I believe we can now focus on automating or streamlining the effort we put into z-stream releases.

      Acceptance Criteria:

      • z-stream process analyzed
      • Process streamlined as much as possible.  Determine what we will keep as is, change, discontinue or automate
      • Tasks created in Jira to track what can be automated (if extended time needed to complete the automation)

       

      Z stream Process Tasks to Analyze:

      • Release schedule updates in Smartsheets for PP (Keep)
      • Send out communications for shipped/delayed.  (Keep)
      • Version Report for upcoming zstream releases (Keep)
      • PP weekly status updates.  Does anyone in OpenStack look at these updates or will program doc updates suffice? (Keep/Discontinue/Automate?)
      • Reviewing, following up, and managing the Jira Release Criteria dashboard (Keep/Discontinue/Automate?) 
      • FIB, On Errata, Jira status.  Do we continue nagging teams to check there issues or have issues miss the release because of bad Jira data or missing/incorrect FIB?
      • Critical Gaps bugs.  Do we want to make sure critical gaps are fixed in the release or have a plan?  Or not necessary for z streams? Or pus responsibility on POs/SMs? 
      • Provide milestones in the program doc or just link to a smartsheet calendar (Keep/Discontinue/Automate?  Possibly automatic calendar)
      • Follow up on critical gaps and untriaged bugs for zstream releases (Keep/Discontinue/Automate?)
      • Track issues on the Blocker and Exception Board (Keep.  Figure out how to automate or streamline for quicker turnaround)
      • Following up with the requestor to answer initial questions on the newly created ticket. (Automate? Jira Slack integration?)
      • Following up with the CORE team to approve/reject the request. (Discontinue.  Enforce SLA for CORE team or POs?)
      • Following up if additional information is needed for CORE or the requestor. (Discontinue.  Enforce SLA?  Stricter criteria in request?)
      • Tracking the request to completion. (Discontinue.  Enforce SLA?  Stricter criteria in request?  Open issues called out in CORE or PO meeting?)
      • Setting the bug/feature to approved or rejected (Keep. Should this be done by PO now?).
      • Should we think about a RACI to help new POs/SMs and ultimately improve Jira hygiene?

              dhughesgit Denise Hughes
              dhughesgit Denise Hughes
              rhos-core
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: