Complete.Org: Mailing Lists: Archives: freeciv-dev: September 1999:
[Freeciv-Dev] Re: cvs-tags and snapshots
Home

[Freeciv-Dev] Re: cvs-tags and snapshots

[Top] [All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index] [Thread Index]
To: dwp@xxxxxxxxxxxxxx, maage@xxxxxxxxx
Cc: freeciv-dev@xxxxxxxxxxx
Subject: [Freeciv-Dev] Re: cvs-tags and snapshots
From: Reinier Post <rp@xxxxxxxxxx>
Date: Mon, 20 Sep 1999 12:49:53 +0200

On Mon, Sep 20, 1999 at 02:54:48PM +1000, David Pfitzner wrote:
 
> CVS does already allow one to check-out the sources from
> a specific date/time, so you can effectively do this already.
> (There are also nightly snapshots as Reinier mentioned, but
> they are not so useful simply because they don't stay around 
> for long.)

Good point.  Are they identical to the cvs checkouts of the same day?
That would solve the problem.  As a matter of fact, for dates in the
past, snapshots can be created on the fly.  (Trigger the 'snapshooter'
from a CGI script.)

> But I agree that for some purposes it would be more useful
> if we deliberately tag more often than major releases, probably
> increasing the PATCH_VERSION more freely, as Nicolas suggested. 
> (Increasing the version number often would allow increased 
> profile on eg freshmeat, too ;-)

But it involves some coordinated playtesting, doesn't it?

[...]

> (Although, if people get into the habit of creating patches
> vs a recent tag, rather than vs "current", that could make
> it _harder_ for the maintainer(s) to merge patches into "current",
> simply because the patches will be typically created slightly
> "older".)

Well, the idea of using snapshots is to be able to publish a patch that
is guaranteed to work on a known version.  I don't want to retrieve a
patch and then have find a suitable CVS version by guessing.  Before
it is checked in, I've always assumed, the author will update it to
work with current CVS.

-- 
Reinier

[Prev in Thread] Current Thread [Next in Thread]