Re: 2.4.x and 2.6.x ... next steps
> On Sep 12, 2018, at 10:27 AM, Stefan Eissing <stefan.eissing@xxxxxxxxxxxxx> wrote:
> I feel myself in agreement with Bill that trunk needs to be where 2.5.x is born.
It is. That should be clear in the proposal.
What should also be clear is that there is a LOT in trunk that should be in 2.4.x and has nothing to do with 2.5/2.6/3.0/next-gen. So backporting that stuff HELPS midwifing 2.5/2.6!