Pulling this out as a proposal:

I propose that we track all backports in 2.4 STATUS as we currently
do. Each backport is time-tagged and we operate under a lazy
consensus. Assuming no -1 votes within 96 hours, the backport
can be applied to 2.4.x. If the backport gets 3 +1 votes sooner
than that, then it can be applied asap...

As with ALL patches, any commit can be reverted for good
technical (or legal) reasons.

[ ] +1: Agree with this proposal (to start post 2.4.5 release)
[ ] -1: Disagree with this proposal (and why)

Reply via email to