please merge+tag newest branches first

Is your feature request related to a problem? Please describe. Sometimes fixes are merged and tagged on older branches before merging and tagging on newer branches.

For example in https://github.com/ceph/ceph-ansible/pull/3352 , the backport to stable-3.1 was merged and tagged as v3.1.11, but the backport to stable-3.2 was not merged. If users upgraded from v3.1.11 to v3.2.0, they would experience a regression.

Describe the solution you’d like Would you please merge and tag fixes on the latest branches (eg. stable-3.2) before merging and tagging on older branches (eg. stable-3.1) ?

Is there any way to have Mergify enforce this? Is that an RFE to Mergify?

[ktdreyer]

Thanks for explaining @leseb . If there is anyone who is pressuring you to provide fixes on older branches who cannot wait for it to land in newer branches, I would ask that you please have that person bring their concerns directly to me. I would be happy to have a conversation with anyone in Red Hat or elsewhere who is pressuring us to ship fixes in older branches first.

Fixing in the newest version first is something that we must do for all projects (ceph, nfs-ganesha, the kernel, etc).

Given the number of changes that we’re tracking in ceph-ansible, and the number of stable branches we’re tracking, the risk of regressions for QE and our users is high. When the bugs are high-pressure like the ones mentioned above, it means that we’ll incur an even greater cost if we also introduce a regression in that code path or feature.

[ktdreyer]

Cool, thanks.