On 2012-11-26, at 5:38 AM, Matthias Melcher <m...@matthiasm.com> wrote: >>> ... >>> "Software releases shall be generated for each successfully completed >>> software trouble report." >>> >>> although this is not like the current (past) practice. >> >> >> Well, I suppose we *could* sort of claim that the weeklies fulfil that >> role... >> >> >>> Shall we change the CMP? >> >> >> Maybe; though evidence suggests that no one would notice the changes anyway! >> ;-) > > LOL, yes. > > In the past, we would generate new patch releases whenever *all* STRs were > fixed. Hence the enormous time between patches. I would suggest to release a > new patch whenever a critical STR (preferable several critical STRs within a > short period, say a week) has been fixed.
The FLTK CMP came from the CUPS CMP, which has "grown" over the years from its roots. One of the things we did was drop the "one release per change" and "no bug unfixed" verbiage. Instead, we adopted simpler goals - a new patch release every 6-8 weeks, no release containing a P4 or P5 bug unless absolutely necessary - and that allows us to keep updates coming out as needed without (too long) delays or too much overhead for keeping new releases coming out. Seems like this kind of a yardstick could be used for FLTK as well... _____________ Michael Sweet _______________________________________________ fltk-dev mailing list fltk-dev@easysw.com http://lists.easysw.com/mailman/listinfo/fltk-dev
