[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: How-to code freeze in Subversion?

From: Gary Feldman <g1list_1a_at_marsdome.com>
Date: 2004-08-25 03:31:36 CEST

Asif Haswarey wrote:

> First of all, I'm wondering if there is a google group for Subversion?

Google groups are just Usenet newsgroups. Many popular clients can deal
with newsgroups and mail similarly, but mailing lists are easier to
manage. For a good archive of this mailing list, see
http://www.contactor.se/~dast/svnusers/ .

> I want to be able to do a code-freeze, where I am able to get a working
> copy of each file revision, such that I can build a program for a previous
> version.

The convention way for freezing snapshots in many source control
systems, including Subversion, is to use tags. For Subversion,
typically there is a tags directory near the root of the repository, and
you just do a copy of a stable tree into that tags directory, giving the
tag a unique name.

See http://svnbook.red-bean.com/svnbook/ch04s06.html for an explanation.
  Note that if you follow their example, which is a URL to URL copy, you
need to make sure that no one else checks anything in until you start
the copy, otherwise you'll get their new version. It is easier and
faster to use that method, and I use it myself, but I'm on a small
development team so I can just ask people to hold off on checkins for a
bit. It is, however, safer to create the tag copy from a working copy
that you know is correct. This is discussed earlier in the chapter,
under branches.

Make sure you have a good naming convention for tags, otherwise things
will get confusing quickly. Personally I'm fond of the convention that
tags are in UPPER CASE, branches in lower case, but that's just a start.


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Aug 25 03:32:23 2004

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.