Uploaded image for project: 'OpenShift Builds'
  1. OpenShift Builds
  2. BUILD-943

[shipwright-io/build] [SHIP-0038] Use Release Branches for Releasing

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Critical Critical
    • builds-1.1
    • builds-1.0
    • shipwright
    • 0
    • False
    • None
    • False
    • SECFLOWOTL-159 - Shipwright v0.13.0 Release
    • Release Note Not Required
    • Upstream Only
    • Builds Sprint #3

      [2200351440] Upstream Reporter: Adam Kaplan
      Upstream issue status: Open
      Upstream description:

      Is there an existing feature request for this?

      • ☒ I have searched the existing feature requests

      Is your feature request related to a problem or use-case? Please describe.

      Per SHIP-0038, we are changing our release process to ship official releases from a release branch, rather than from main.

      Describe the solution that you would like.

      • CI and release scripts can be run on a release branch (with release-v* pattern)
      • Release workflows must use an appropriate release branch and/or git reference (cannot blindly use latest commit from main)

      Describe alternatives you have considered.

      See SHIP-0038 for discussion

      Anything else?

      Part of shipwright-io/community#85


      Upstream URL: https://github.com/shipwright-io/build/issues/1555

              adkaplan@redhat.com Adam Kaplan
              upstream-sync Upstream Sync
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: