Emmanuel Blot kirjoitti:
>> so if you release now, and then do a bugfix release by changing the
>> context like cmlenz suggests, who would care? and then release
>> something further developped with maybe an idea of cboos in it
>> discussed?
>
> The developers team use a version numbering scheme that carries some meaning:
> 0.11.1 and subsequent 0.11.x releases should not break APIs that will
> be available in 0.11. This scheme won't be changed for the sake of
> releasing earlier.
>
> 0.11 needs to be released, everyone's expecting it, but it needs to be
> a well defined object.
>
> If you don't care about the numbering scheme, you can check out the
> code from the trunk.
>
> As a user, I do care about the version numbering.
> Users are already confused about which plugin they can use with a
> given release of Trac. I can't imagine the support nightmare
> (MailingList and tickets) if the APIs vary over bug fix releases...
>
> So, as a short answer to your question ("who would care"), I would and
> I'm bet (hope?) I'm not the only one.
Let's add one more cook to this soup... (Hmm, maybe subject change
should take a place...)
As an (end) user I really don't give a shit about version numbers etc.
since I don't install anything, configure anything. I just use it and
I'm happy with that. Maybe only time I need to care about version number
is when I find a bug.
As an administrator I don't pay much attention to version numbers if
they're consistent. Specially with tool like Trac that relies much on
3rd party plugins there definitely must be some sort of meaning of
version numbers.
As a (plugin) developer I'll care more than enough about version
numbers. I want to have my plugins as long lifespan as possible without
any changes. Otherwise I'll end up in major upkeeping hell with loads of
different versions. Like currently people uses 0.9.x, 0.10.x and 0.11dev
there is frequent questions about does plugin "magicthingy" work on
version 0.x.y when it will be ported and so on.
Regarding to Noah's comment (e-mail arrived while I wrote this), I know
that devs are never happy with new thingies since there will be always
something that could be done better. :D
But I think just "good enough" is more correct term here...
Above gives good reason to me why I like to use test driven development
model.
--
Jani Tiainen
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
