Yes, that's what I mean, do it when a fix is needed.
Not sure why it needs a special developer to do a CVS one-liner though.
Surely the overall project manager can do it?
Some checks could be scripted to verify that it is really identical.
Burke, S (Stephen) wrote:
> Testbed Support for GridPP member institutes
>> [mailto:[log in to unmask]] On Behalf Of Simon George said:
>> It's possible to apply two CVS tags to the same revisions of the code.
>> (I expect you know this.)
>> So doesn't this mean that a new one could be created simply
>> by tagging
>> the previous version in CVS with the new tag and cranking the
>> handle on etics?
>
> Yes, but to do that routinely would be a lot of extra work, and it would
> also make it hard to follow the evolution of the code because the tags
> would keep jumping around. And you might well introduce new bugs by
> accidentally releasing an older version instead of a fixed one, or
> getting dependencies wrong.
>
> On the other hand, doing that *after* you know you have a problem is
> certainly possible in many cases, and is likely to be the best solution
> if it's feasible. However, I think part of Markus' argument is that it
> needs the developer to do that so it's not in the control of SA3. Also,
> since you are in fact making a new version even if supposedly identical
> to a previous one, you have the usual questions about whether it would
> be safe to release it without certifying it - "it's a trivial fix,
> nothing can go wrong so we don't need to test it" is often a recipe for
> disaster :)
>
> Stephen
|