On Sep 17, 2007, at 17:55, Daniel Jimenez wrote:
> We have a svn rep, which contains the typical structure
>
> SVNRep
> |
> |--Branches
> |
> |--Tags
> |
> |--Trunk
> |
> |--Project1
> |
> |--Project2
>
>
> 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).
>
> 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.
>
> (2) If a new user arrives and completes a checkout of the SVNRep/
> Truck,
> she/he will not get archived/freezed projects.
>
> (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 ???
>
> I guess the structure would look like these ???
>
> SVNRep
> |
> |--Archive
> |
> |--Project1
> |
> |--Branches
> |
> |--Tags
> |
> |--Trunk
> |
> |--Project2
>
> Any help suggestion on how to achieve this would be appreciated.
The structure you show at the end looks good to me. You could use the
word "Archive" (or "Archived") or "Old" or "Deprecated" or "Obsolete"
or "Inactive" or anything like that. To move Project1 there, you would:
svn mv url://to/SVNRep/Trunk/Project1 url://to/SVNRep/Archive -m
"Moving Project1 to the archive"
When anybody uses "svn update" in their working copy of the entire
Trunk, their copy of Project1 will be deleted (unless they have local
modifications, in which case those modifications will be retained,
though to commit them they'll have to "svn switch" their working copy
to the project's new location in the archive).
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Sep 21 19:49:42 2007