Mark Wedel wrote:
Using tags may actually make more sense.
Right now, when I make the actual release, I tag the files, so you
can do something like 'cvs checkout -r rel-1-7-0'.
But as described about, not until a change happens do you need a
branch. So what should probably be done is at the 'code freeze' time
do a cvs tag can-1-8-0 or something. Thus, if nothing changes, that
can be tagged again as rel-1-8-0 ( can = candidate, rel=release). So
if changes are made to CVS head, no big deal - the can- tag is still
there to get the files to release. If a fix needs to be backported,
the can- tag can be used to find the point to make the branch from.
I think this would be a great way to do things. I'm currently not
familar with using tags in CVS, however I don't think it would be any
real trouble to learn.
If other people want to help with releases, that would be great.
Having a more frequent (quarterly) release schedule would also be good.
Even people taking some portiosn of the release (maps, archs) reduces
the effort a bit on my side - those bits aren't really hard, but if I
save myself 15 minutes, that is always nice.
I could certainly help with some part such as maps or archs etc.
Alex Schultz
_______________________________________________
crossfire mailing list
crossfire@metalforge.org
http://mailman.metalforge.org/mailman/listinfo/crossfire
