On Oct 11, 7:21 am, Jeroen Ruigrok van der Werven <[EMAIL PROTECTED]
nomine.org> wrote:
> -On [20071010 21:18], Emmanuel Blot ([EMAIL PROTECTED]) wrote:
>
> >So, as a short answer to your question ("who would care"), I would and
> >I'm bet (hope?) I'm not the only one.
>
> As an administrator for an ISO 13485 certified company I do care about
> releases and release numbering. The same will probably apply for any
> ITIL-using company:
>
> Any update of the software on the system to a newer version needs to be
> tracked in a change request. Too frequent updates with a mentality to use
> version numbers willy nilly will be a sincere pain in the ass for anybody
> caught in the above.
>
> I am all for releasing a bit more often than the current way, but don't get
> overzealous and use the tiny version number for a simplistic counter for the
> patch-du-jour.sorry for confusion - we care a lot about consistent version numbering as we care a lot of trouble free plugin usage. we would appreciate a lot if the version number increases if the api changes. just the tag would be enough (i.e. no release), so that all compatible things also are able to tag. especially if an api is around for enough time so that things exist which use this api - like it is with trac-0.11-dev. and, it would be very nice if always the same position increases if the api changes in a not backwards compatible way. in case of trac it is the second (0.10 --> 0.11 --> 0.12), isn't it? the only thing we do not care is what functionality / api is in a version called 1.0. the only requirement would be that it runs stable. rupert. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Development" 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/trac-dev?hl=en -~----------~----~----~----~------~----~------~--~---
