On 15.11.2010, at 11:57, Peter Åstrand wrote: > > I'm very surprised to see "Will Not Fix". Can you explain the reasoning > behind this? The patch is small and unintrusive and fixes a major problem > which will otherwise lead to a segfault. > > In general, IMO, you shouldn't close bug reports without adding a comment. > > Yes, I saw the first line about "POST ANY RESPONSES TO THE LINK BELOW", but > this is not possible, since the STR is closed!
The reason is simple. The FLTK 1.1 branch is closed for good. It's a great branch and we kept fixing bugs until we have not heard of crashes for over a year. We decided that FLTK 1.1.10 would be the last in the FLTK 1.1 line. A 1.1.11 release would eat up many hours of my time that I can't put into 1.3. FLTK 1.3.0 is 99% source code compatible to FLTK 1.1 plus a huge amount of bug fixes and improvements. It will be released before the end of the year and will fully replace FLTK 1.1 . Nothing should hold our users back from migrating their projects over to FLTK 1.3 . So, in conclusion, keeping multiple branches alive takes time. Time that we need for fixing bugs and adding new features in the *current* version. I personally believe that it is better to fix and release 1.3 than to fix 1.0, 1.1, and 1.2 (because they also have the bug you describe). Maybe one of the other core developers want to make a release? - Matthias _______________________________________________ fltk-bugs mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-bugs
