I would feel much more comfortable if the default behavior was to always
port back in reverse order without skipping a support branch. This makes it
much harder to forget poring to a support branch. Few things are more
frustrating to users than upgrading to a new patch release to get a bug fix
and
Sound like there is no need to clarify or amend what is already spelled out in
RFC[1]:
* Backports can be made to dormant support branches without requiring a
proposal or votes, subject to the "exercise good judgement" clause in the RFC.
* Backports to multiple support branches can be made in any
I noticed a recent change on support/1.12 that was not preceded by a backport
proposal.
I re-read the Shipping Patch Releases RFC[1] which was adopted earlier this
year, and it doesn’t seem to mention anywhere that a backport proposal is
required for “dormant” support branches.
However, it doe