> On Sep 12, 2018, at 10:27 AM, Stefan Eissing <stefan.eiss...@greenbytes.de> > 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!
- Re: 2.4.x and 2.6.x ... next st... Christophe JAILLET
- Re: 2.4.x and 2.6.x ... next st... Graham Leggett
- Re: 2.4.x and 2.6.x ... nex... Daniel Gruno
- Re: 2.4.x and 2.6.x ...... William A Rowe Jr
- Re: 2.4.x and 2.6.... Eric Covener
- Re: 2.4.x and 2.6.... Jim Jagielski
- Re: 2.4.x and ... William A Rowe Jr
- Re: 2.4.x and ... Graham Leggett
- Re: 2.4.x and ... William A Rowe Jr
- Re: 2.4.x and ... Stefan Eissing
- Re: 2.4.x and ... Jim Jagielski
- Re: 2.4.x and ... Jim Jagielski
- AW: 2.4.x and 2.6.x ... next st... Plüm , Rüdiger , Vodafone Group
- Cool Stuff In trunk: (Was: ... Jim Jagielski
- Re: Cool Stuff In trunk... Stefan Eissing
- Re: Cool Stuff In ... Yann Ylavic
- Re: Cool Stuff In trunk... William A Rowe Jr
- Re: Cool Stuff In ... Jim Jagielski
- Re: 2.4.x and 2.6.x ... next steps William A Rowe Jr
- Re: 2.4.x and 2.6.x ... next steps Christophe JAILLET
- Re: 2.4.x and 2.6.x ... next steps Stefan Eissing