Uploaded image for project: 'Red Hat Internal Developer Platform'
  1. Red Hat Internal Developer Platform
  2. RHIDP-2656

Document cherry picking process for plugins and showcase repos

Prepare for Y ReleasePrepare for Z ReleaseRemove QuarterXMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Critical Critical
    • 1.2
    • 1.2
    • Build
    • None
    • 1
    • False
    • Hide

      None

      Show
      None
    • False
    • RHDH Core Team 3258

      Story

      As a developer, I want a clear understanding of the cherry picking process during code freeze so I can ensure my fixes are delivered to the right release

      Background

      This has been a common theme from release to release, where there is a lack of understanding on when to cherry pick.  The risk here is that fixes will be overlooked and will miss getting into our deliverables. 

      Dependencies and Blockers

      QE impacted work

      Documentation impacted work

      Acceptance Criteria

      process documentation updates

      • What issues should be cherry picked?  Critical/High fixes, customer impact
      • What is approval process and who should be involved?
      • Should the cherry picked PR be posted on Slack or is that an escalation route?
      • Should plugins be cherry picked?

      optional slack bot reminders during code freeze with the link to process

              nickboldt Nick Boldt
              ktsao@redhat.com Kim Tsao
              RHIDP - Core Platform
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: