Hi Jay,

These are the branches OpenShift uses for its downstream versions of Metal3 (extracted from our internal docs):

ironic bugfix/21.0
ironic-inspector bugfix/11.0
ironic-python-agent bugfix/9.0

ironic bugfix/20.2
ironic-inspector bugfix/10.12
ironic-python-agent bugfix/8.6

ironic bugfix/19.0
ironic-inspector bugfix/10.9
ironic-python-agent bugfix/8.3

ironic bugfix/18.1
ironic-inspector bugfix/10.7
ironic-python-agent bugfix/8.1

We use them, because OpenShift releases are not aligned with OpenStack ones, so more often than not, we need to have a slice of the master branch. Having bugfix branches allows us to collaborate on bug fixes upstream, rather than on forks in github.com/openshift. Please reach out to Riccardo, Iury or myself if you have any questions on OpenShift's usage of Ironic.

Dmitry

On Tue, Sep 20, 2022 at 10:32 PM Jay Faulkner <jay@gr-oss.io> wrote:

Hey all,

Ironic releases intermediate bugfix releases during the cycle. These are consumed by some packagers and standalone users of Ironic.

Today, using Ironic as an example, we have 4 active bugfix branches:
- bugfix/21.0 and bugfix/20.2 are between yoga and zed
- bugfix/19.0 is between xena and yoga
- bugfix/18.1 is between wallaby and xena

We are considering cleaning up some of the older bugfix branches, to reduce stable maintenance load -- but we would like to poll you all first: Is anyone consuming these releases downstream? If so, which ones and why?

This will be useful input to whatever action we decide to take!

Thanks,
Jay Faulkner

Red Hat GmbH, Registered seat: Werner von Siemens Ring 12, D-85630 Grasbrunn, Germany  
Commercial register: Amtsgericht Muenchen/Munich, HRB 153243,
Managing Directors: Ryan Barnhart, Charles Cachera, Michael O'Neill, Amy Ross