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

Re: Archiving Projects (End-Of-Life)

From: David Weintraub <qazwart_at_gmail.com>
Date: Mon, 13 Dec 2010 16:23:06 -0500

On Mon, Dec 13, 2010 at 3:04 PM, Johan Corveleyn <jcorvel_at_gmail.com> wrote:
> Hi,
> I'm wondering if there is a (de-facto) standard way of "end-of-lifing"
> projects in an SVN repository, or any suggestions for this from other
> users on this list ...
> I know I could just "svn rm" them, but some of the "project owners"
> feel a little bit uneasy about that.

Do they know that doing a "svn rm" doesn't actually remove those
projects from the repository? All "svn rm" does is remove them from
the HEAD of the repository. They can still access all the history,
tags, branches and what not by simply using the -r <revision>
parameter when you do a Subversion command. And, they can find out the
revision by doing a "svn log".

However, if that's to scary for them, create an "obsolete" folder and
move all the projects in there. Then, via pre-commit hook or
configuration, make all files and directories under "obsolete"

+--obsolete (Whole subtree is read only)
| |
| trunk
| branches
| tags
+--trunk (Still read/write)
+--branches (Still read/write)
+--tags (Still read/write)

That'll get the files out of the main project tree, prevent further
changes in the code, yet still allow the developers to examine the
code and reminisce about the good ol' days when men were men and UUCP
was king.

David Weintraub
Received on 2010-12-13 22:23:45 CET

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.