Uploaded image for project: 'Quarkus'
  1. Quarkus
  2. QUARKUS-3258

Release only members BOMs that have changed since the last release and let each member use its own versioning

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Major Major
    • 3.y-Jumanji.GA
    • None
    • platform, team/eng
    • None
    • Allow individual versioning of platform member BOMs
    • False
    • None
    • False
    • To Do
    • ---

      To avoid the number of SP releases, we may consider changing the platform release model from releasing all the member BOMs together under the same shared versionĀ  whenever there is a change in any member BOM to releasing only the member BOMs that have actually changed since the previous release. This change would imply that each member BOM would use their own versioning.

      Here is a summary of what 2.13 platform releases include if we took this approach for 12.3 https://docs.google.com/document/d/1NwZ-n7nBdP0lnYznEZssur0bIlBBENFp0DXlr_7Xc4w/edit#heading=h.6t9i9qxc2chf

              olubyans@redhat.com Alexey Loubyansky
              olubyans@redhat.com Alexey Loubyansky
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: