Matthias Melcher wrote: > Am 02.07.2009 10:15 Uhr schrieb "Albrecht Schlosser" unter [...] > >> 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. > > Yes, very well. Do the version numbers need to be increased internally?
Done (version numbers and such), see http://www.fltk.org/newsgroups.php?gfltk.commit+v:7179 ANNOUNCEMENT, README, ... still need more work. >> STR #1986 would probably be difficult to fix, maybe we should postpone this >> one? > > Scratch it. Thi is nothing we can solve in 1.1. Okay, I'll see if I close it or move it to FLTK 1.3 or 1.4. >> 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... > > I don't know, but it would probably work better. I will try to take a look > at this asap. okay. >> STR #2138 looks like a user problem, maybe we should close with the >> appropriate >> message... > > VC8 anyone? > >> 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 ... (?) > > If you could take a quick look. That can't be too diffucult to solve?! I'll see what I can do, but maybe not before the weekend. I also need to fix some docs that have been forgotten... >> 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 >> ;-) > > Um, yes, I think we should do an RC because that triggers better testing, > especially of the stuff that we just recently fixed. I would not wait too > long for reports to trickle in though. Once we are certain that the version > has not gotten worse, we should finalize. Well, that's okay, let's make an RC then. > Great then. Let's kickk it off. Yep :-) Albrecht _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
