Sounds like a good plan. The recent GTK+ 3 work is just bug-fixing in the experimental build, so shouldn't impact on the release schedule.
AV On 6 May 2016 9:59 p.m., "Bryce Harrington" <bryce@...961...> wrote:
On Wed, May 04, 2016 at 01:18:23PM +0100, Alex Valavanis wrote:
Hi All,
Just wondering if there are plans to freeze development yet? I think we're getting close to having a working CMake build... are there any "must have" features that are not yet fully implemented in 0.92, or can we push on with fixing-up the remaining bugs and releasing?
I'm quite eager to make the switch to a hard C++11 requirement and default to Gtk+ 3, so the sooner we can get 0.92 out, the better :)
Best wishes,
We had a quite productive meeting this morning. I'll be posting various followup bits through the weekend, but wanted to float a couple items we felt were worth proposing:
How do folks feel about a feature freeze in, say, a week? Are there any WIP's that would get disrupted if we did that?
Regardless of when we feature freeze officially, I'd strongly suggest any currently underway development be wrapped up asap, and anything that's been recently added (e.g. Gtk3 work was mentioned) be brought to a releasable state. That could mean disabiling it by default or even reverting the changes for now and save them for 0.93 worst case.
Josh is going to boil down a list of release blocking bugs. Send him ones you think must be on the list, but please be extremely selective, we don't want to get the release bogged down too much on bugs.
Experimental branch - we're thinking we'll try to make the release process go quick enough that we can avoid doing an experimental branch this cycle, and just encourage folks to work on side branches for now. We can always set one up later on if there's a demand for it.
Comments welcomed on any of the above. I'll be posting a release plan either today or this weekend, and nail down the decisions for the above, so if you've got input on any of the above, please share asap.
Bryce