> I'm wondering if there is a (de-facto) standard way of "end-of-
> projects in an SVN repository, or any suggestions for this from
> users on this list ...
> With End-Of-Life I mean there will be no further maintenance on
> project, no more development, no more releases or patches, no more
> users. It's really dead. But sometimes one might want to take a
> at the old code, check out its history, maybe even resurrect it,
> I would like to get those projects out of sight, so it's more clear
> what the active projects are. (I'm not talking about
> to reclaim disk space or anything like that, quite the contrary: I
> want to have them still available, just ... less visible).
> I know I could just "svn rm" them, but some of the "project owners"
> feel a little bit uneasy about that. They consider it "probable"
> they will need to take another look at them sometime in the future.
> And as we all know, it's not so easy to find a deleted
> file/directory/project again (to find out what the latest revision
> in which the project still existed).
> My repository is currently structured as:
> But I think the question is more or less the same if it's
> in the other standard way (projects/TTB).
> Currently I have two options in mind:
> - Move the EOL'ed projects to a new directory "archive", a new
> directory next to TTB.
> - Move the EOL'ed projects to a tag (maybe also in an "archive"
> subdirectory, under tags). If it ever needs to be resurrected, it
> be easily copied from that tag.
> Thoughts? Other ideas? Pros and cons?
Two options I can think of.. one simple, one will need admin access...
1. Create a folder in your repository named (end of life) and move the project folder there.
2. Dump the repository, use dumpfilter and import it into an "end of life" repository, then RM it from your main repo.
Received on 2010-12-13 22:01:02 CET