Uploaded image for project: 'AMQ Streams'
  1. AMQ Streams
  2. ENTMQST-6795

[PROD] Automatically set bundle channels based on build history

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • None
    • None
    • None

      The bundle channels are currently fixed in the dist-git repository. When an LTS release is superseded but still maintained, we need to remove bundles from the LTS from the `stable` channel since adding it there would violate SemVer.

      Using the process that queries Brew for the next release and the `replaces` value, we can also determine whether the current release should be in `stable` or not.

      When multiple LTS releases are being supported, the older releases should also no longer be added to the `X.x` channel, assuming there are multiple LTS releases within a major version.

      In summary:

      • only add a bundle to `stable` if no bundles with a higher semver in Brew have been released
      • only add a bundle to a major release channel (e.g. `amq-streams-2.x`) if no bundles with a higher semver with the same major version in Brew have been released

      This task also applies to the Console, Proxy, and Flink operator bundles.

              Unassigned Unassigned
              medgar@redhat.com Michael Edgar
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: