Monday, June 21, 2010

Preparing for 2.9.1

Sorry for lack of posts summarizing the recent wxWidgets development progress and here, to compensate, is a post about an upcoming development: we're finally going to release 2.9.1 soon. This release will include many of the things previously discussed here, notably new debug build handling, thread-safe wxLog, new wxInfoBar class and so on.

It will also probably be the penultimate release before 3.0 as the current thinking is to release 2.9.2 after merging the work of the students on GSoC projects this summer some time in September and then follow with a 3.0 release before the end of the year. So testing and finding bugs and, even worse, regressions compared to the old 2.8 versions would be very welcome.

The schedule for this one is to make a release candidate before the end of this week and the final one on July 12 or, if any important problems are found with the RC, on July 19 to give us some time to hide them under the carpet fix them.

5 comments:

ralg said...

Great news, nice to know 2.9.1 is around the corner but, having 2.9.2 by Sept. and 3.0 by the end of the year isn't way too optimistic?

VZ said...

We want to try to make the releases faster than usual, there is really no point in waiting for so long between them. Not a guarantee that we'll succeed, of course, but we'll try nevertheless.

ralg said...

Well those are even greater news, hope it to happen as scheduled

Begemot said...

There is a couple problems with menu in current trunk

http://trac.wxwidgets.org/ticket/11657
http://trac.wxwidgets.org/ticket/12033

I think it should be fixed before 2.9.1.

Regrettable for me, but I can't switch to new release, because I can't use broken menu in production code, users won't understand me :)

VZ said...

Unfortunately the menu related bugs are there since a couple of months already and I don't think they're going to be fixed very soon. So we'll still release 2.9.1 even if they're not fixed until then (as seems likely) because there are many, many other things which need to be tested.

The first of these bugs will definitely be fixed before 3.0. The second one seems much less critical so I don't know about it.