All, I'd like to have a new FLTK 1.1 release soon, because there are so many bug fixes in svn that we should IMHO push a new release.
I'm prepared to do the version update, the only thing that needs to be done is to commit it. Would this be the right time to do it now? BTW: In earlier releases we (i.e. Mike or Matt ?) changed the version numbers short after each release, so that subversion had the new version numbers, as it is also shown in the CHANGES file. Shouldn't we do this now and in the future again (of course also with 1.3.x)? --- Current status is 5 open STR's (and decreasing, thanks, Matthias!). STR #2135 looks as if it is fixed already. STR #1986 would probably be difficult to fix, maybe we should postpone this one? STR #2203 looks like it can be done easily by backporting the fixes in FLTK 1.3, if the Mac OS specific --post stuff is okay for FLTK 1.1 as well (I think so, but I'd appreciate a confirmation). Anybody? If okay, I can do it shortly... STR #2138 looks like a user problem, maybe we should close with the appropriate message... STR #2130: I'm not sure what to do, but I'd like to take a look at this. Maybe this one can't be fixed completely for 1.1, but ... (?) Anyway, even if we can't fix all the STR's in a short time, I'd like to have a release soon, maybe with a "known bugs" section in the README file. Having fixed about 25 STR's and a security update for the embedded png lib looks much better for me than waiting until bug #30 is fixed ;-) Thoughts, anybody ? Last question: do we need RC's? According to the CMP [1] this wouldn't be necessary, but common practice of the last years was that we had RC's even for "patch versions". But we also didn't fix one bug at a time for a new release ;-) Albrecht [1] http://www.fltk.org/cmp.php#SOFTWARE_RELEASES _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
