On 2009-08-20, at 22:20, Ullrich von Bassewitz wrote: > > * There should be a compelling reason for a new major release. > Maybe I'm > wrong, but I think, people expect that. Just "a few default > behaviours > changed" is not really enough. > IMHO changes, which trigger some noticeable incompatibilities do qualify for that. If not for any other reason than to draw the line between versions, which allow the "old" behaviour, and those which require "new" one by default. If those add some extra possibilities on top - should be very much acceptable as a trigger for new version. > * There are a few things I want to go into a new release. Nothing > big, a few > days of coding and debugging anway. Unfortunately a day of coding > cannot be > replaced by 16 half hours, so I need real spare time. Yes - I think we all concur here... > * Changing stuff (especially if code generation and optimizations are > involved) is error prone. While I do understand that testing is > difficult > if there are incompatible changes, rushing out only loosely > tested stuff > gives me a bad feeling. Usually, bug reports start coming in when I > release a new version. I'm still trying to find a way to get > these bug > reports *before* the release. Yes - that's of course very valid concern. -- SD! ---------------------------------------------------------------------- To unsubscribe from the list send mail to majordomo@musoftware.de with the string "unsubscribe cc65" in the body(!) of the mail.Received on Fri Aug 21 13:04:27 2009
This archive was generated by hypermail 2.1.8 : 2009-08-21 13:04:29 CEST