On 09.02.2015 16:44, Julian Foad wrote: > Branko Čibej wrote: >> All right, it's been three weeks. During this time some massive code >> churn has happened on trunk, and a couple branches (pin-externals and >> reuse-ra-session) are assumed to be merge candidates for this release. >> >> None of the above is really necessary for a 1.9 release, but since it's >> here, let's please stabilize trunk for the branch. > I'd like to say something > stronger. It would be lovely if those pieces of work that are still in > progress on branches get released in 1.9, and I hope they will, but let's not > fall into the old trap of starting with an assumption that they will. Rather, > let us start with the assumption that 1.9 will be released 5 weeks from > today, and start concentrating right now on the activities needed to achieve > that. If the work-in-progress gets included as well, that's great, but we all > know from experience that work that seems to be nearly finished nearly always > isn't.
Agreed. I'm now working writing down a formalized description of the release process we talked about in Berlin back in 2013, in such a way that it should help us plan development and releases better. In the certain (though forlorn) hope that we can actually release 1.10 about 6 months after 1.9. Pending consensus about the process, of course. -- Brane
