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

RE: RE: Howto freeze or archive a project

From: Bicking, David (HHoldings, IT) <David.Bicking_at_thehartford.com>
Date: 2007-09-18 14:57:25 CEST

> -----Original Message-----
> From: Daniel Jimenez [mailto:d.jimenez@comvision.net.au]
> 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.
> > You can't really force-delete anything from the client system.
> I have tested this and it works.

This is a confusing assertion. Does it mean you confirmed that one
can't force deletions in the client system, or that you have experience
in which you proved that you can? If the latter, how?

> 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 product.
> 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.

One option is to leave it where it is, and change permissions such that
everybody but a select few cannot access that project. I am very wary
about copies because of the effect it has on filtering dumps. Another
benefit is that you don't have to worry about your next issue:

> 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.
> Regards
> daniel

I presume you also have a folder per project in Branches and Tags so you
can keep track of them. Still, all you need to do is specify the
workspace location manually for those archived projects if the default
behavior isn't desired.

This communication, including attachments, is
for the exclusive use of addressee and may contain proprietary,
confidential and/or privileged information.  If you are not the intended
recipient, any use, copying, disclosure, dissemination or distribution is
strictly prohibited.  If you are not the intended recipient, please notify
the sender immediately by return e-mail, delete this communication and
destroy all copies.
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Sep 18 14:57:48 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.