> thanks for fixing the bugs so quickly. > > Maybe you could make use of the 'beta' and/or 'release candidate' (rc) tag in > the version number, that's grown quite popular. So, say you want to release > 1.4, but didn't to too much testing (and want the community to test), you > could mark it '1.4rc1' first. If there have been bugs that needed fixing, you > could release another release candidate, '1.4rc2'. Only after this has been > without bugs that need urgent fixing for, lets say, more than a week, release > it as 1.4. This would help people determine the amount of testing that went > into the version, which is especially important for distribution's packagers > (who hate updates without version number changes ;) ). > > Or maybe 1.3.1. Anyway, releasing different code under the same version may lead to some mistakes. Dmitriy
--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Semantic Forms" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/semantic-forms?hl=en -~----------~----~----~----~------~----~------~--~---
