> > > We propose that between the September freeze date and beta, a new branch > would not be created and trunk would only have bug fixes and performance > improvements committed to it. >
+1, like really yes!! because it's a step towards a more stable-master project. If trunk is focused on stabilising (which ideally it shouldn't have to, if stable-master were true) then new features remaining in their respective branches shouldn't be a big cost or risk (nor seen as anything negative). And hopefully any additional practices/lessons learnt from during the freeze period get carried on for good. Although, and unfortunately, there's just not the testing infrastructure available to the public to ensure feature branches are solid before merging. But I struggle to see that as an excuse to only "stabilise" on release branches. 2ยข, mick
