> On Nov 1, 2019, at 11:59 AM, Luca Toscano <toscano.l...@gmail.com> wrote: > > Il giorno mar 29 ott 2019 alle ore 18:31 Graham Leggett > <minf...@sharp.fm <mailto:minf...@sharp.fm>> ha scritto: >> >> On 29 Oct 2019, at 15:51, Jim Jagielski <j...@jagunet.com> wrote: >> >>> My only question regards workflow w/ trunk. Right now, I think we all agree >>> that there are codepaths and features in trunk that are not as stable as we >>> would like. Which is fine... trunk is CTR. But we do need some way to vet >>> those changes (ie, we need to "R" all those "C"s). Some will be accepted, >>> others not. Into what branch do those accepted go? And for the things not >>> accepted for eventually inclusion in 2.5/2.6, do they get removed from >>> trunk? Do they stay in trunk? >> >> As I recall from v2.4, we branched from trunk, and then we removed anything >> we deemed “not ready” from the branch. “not ready” had reasonably simple >> criteria, like “not documented yet”. >> >>> So it seems to me that we need to branch trunk into 2.5.x and "clean up" >>> that branch (items 1-5) and leave trunk alone. >> >> +1. >> >> Let’s get a 2.5 out there, and let people bash on it. > > If this was the previous way of doing things and it worked, +1 as > well. Is there anybody willing to start this process?
I don't want to start any process w/o more consensus about going forward... In particular, branching 2.5.x from trunk...
