On 9/17/07, Daniel Jimenez <d.jimenez@comvision.net.au> wrote:
> Hi,
>
> We have a svn rep, which contains the typical structure
>
> SVNRep
> |
> |--Branches
> |
> |--Tags
> |
> |--Trunk
> |
> |--Project1
> |
> |--Project2
>
I'd consider that atypical. Usually you have trunk, tags & branches
inside each project, not the other way around.
> At this stage, the users via their SVN Client app only see the content of
> the Trunk( obviously they have define the path to the SVNRep all they way
> down to and including the Trunk folder), which is exactly what its required.
> This way they can do an checkout of the entire svnrep and get all the
> current projects.
>
> However, we would like to be able to freeze/archive a project once we decide
> that no more development will be done on that project (for example version 2
> of the product is available).
"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."
> What I would like to know is how do we archive or freeze a project, so that
> after the project (say project1 in the above example) is archived/freezed:
>
> (1) When any user does an update of the SVNRep, the archive project will be
> eliminated from the user's project structure.
You can't really force-delete anything from the client system.
> (2) If a new user arrives and completes a checkout of the SVNRep/Truck,
> she/he will not get archived/freezed projects.
The user will get whatever is under whatever URL they check out and
they have permission to read.
> (2) A user if need be could in the future browse the main SVNRep and see the
> archive folder and projects within that folder, as well as checkout an
> archived/freezed project to complete some bug fix. Commit the fix and re
> archive/freeze the project. How should this be done ???
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.
> 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.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Sep 18 03:44:27 2007