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

RE: Howto freeze or archive a project

From: Daniel Jimenez <d.jimenez_at_comvision.net.au>
Date: 2007-09-18 04:54:39 CEST

Hi Andy,

Ok let me refine the issue further, now that we have a basic understanding
of what I like ;-)

> I'd consider that atypical. Usually you have trunk, tags &
> branches inside each project, not the other way around.

True, but there are dependencies between Projects and RT packages, etc. So
it is easier to have this structure.

> "Freeze" and "archive" are two very different words. "Freeze"
> typically means "keep it around & visible, but don't allow
> update access." Archive is usually "slide it away & out of main view."

Ok so what we are after is to archive, now that I know the difference ;-)
> You can't really force-delete anything from the client system.

I have tested this and it works.
> The user will get whatever is under whatever URL they check
> out and they have permission to read.

True, and this is how we make sure that only currect projects are ever
available to new developers.

> Now you're ignoring the meaning of those words. If the
> project is truly archived or frozen, why are you making
> changes to it? If changes will be required, I'd consider them
> to still be active projects.

Say we have arrived at the end of the life of a product "A". We would like
to archive this project. However, we may have sold 500 copies of it, so we
must continue the maintenance agreement with our clients regarding this

If a client was to report an issue that required a fix, we would like to
know how do we bring this product back to the main trunk, fix the issue, and
the archive the project once more.

So the issue we faced is trying to checkout something that was NOT on the
trunk into the "Projects" folder which IS associated with the main trunk .

> > I guess the structure would look like these ???
> >
> > SVNRep
> > |
> > |--Archive
> > |
> > |--Project1
> > |
> > |--Branches
> > |
> > |--Tags
> > |
> > |--Trunk
> > |
> > |--Project2
> >
> That's pretty much the right approach (you'll use svn mv to put
> Project1 into the Archive directory), but throw in directory
> access controls to stop anyone but repository admins from
> writing to the Archive directory.

Ok will do as suggested.



To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Sep 18 04:54:59 2007

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.