Re: 2.4.x and 2.6.x ... next steps
On 11 Sep 2018, at 20:35, Jim Jagielski <jim@xxxxxxxxxxx> wrote:
> This is what I propose:
> o Later on this week I svn cp trunk over to branches/2.5.x
> o That branch becomes the initial source for 2.6.x
> o trunk remains CTR, whereas branches/2.5.x becomes RTC
> ala 2.4.x (ie: using STATUS and specific, targeted
> backport requests).
> o Backports to 2.4.x only come from 2.5.x
> o We then release a 2nd alpha from branches/2.5.x
> o We get 2.5.x into a releasable stage, whereas we
> svn mv branches/2.5.x to branches/2.6.x
To clarify the above, this describes what we did last time when we went from 2.2 to 2.4. Nothing about the above is out of the ordinary based on what we’ve done in the past.