Re: Context Refactoring

-On [20071010 21:18], Emmanuel Blot (manu.blotgmail.com) 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.

-- 
Jeroen Ruigrok van der Werven
<asmodai(-at-)in-nomine.org> / asmodai
イェルーン ラウフロック ヴァン デル
ウェルヴェン
http://www.in-nomine.org/ | http://www.rangaku.org/
It is the supreme art of the teacher to awaken joy in
creative
expression and knowledge...

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "Trac Development" group.
To post to this group, send email to trac-devgooglegroups.com
To unsubscribe from this group, send email to
trac-dev-unsubscribegooglegroups.com
For more options, visit this group at http://
groups.google.com/group/trac-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Jeroen Ruigrok van der Werven kirjoitti:
> -On [20071010 21:18], Emmanuel Blot (manu.blotgmail.com) 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.

As an extreme case of manufacturing medical devices (that's
what that 
ISO 13485 is all about, right?). You don't run after every
update, don't 
use latest stuff and I wild guess is that you just don't
pick random 
software, start to use it...

I think that main point of this whole discussion is that
0.11 
spesifications got a bit out of hands and got that
not-so-fancy snowball 
effect. And as I have understood this is about to change in
the future...

-- 

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 trac-devgooglegroups.com
To unsubscribe from this group, send email to
trac-dev-unsubscribegooglegroups.com
For more options, visit this group at http://
groups.google.com/group/trac-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

On Oct 11, 7:21 am, Jeroen Ruigrok van der Werven
<asmo...in-
nomine.org> wrote:
> -On [20071010 21:18], Emmanuel Blot (manu.b...gmail.com) 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 trac-devgooglegroups.com
To unsubscribe from this group, send email to
trac-dev-unsubscribegooglegroups.com
For more options, visit this group at http://
groups.google.com/group/trac-dev?hl=en
-~----------~----~----~----~------~----~------~--~---