Repository Redesign Question

When I initially setup my repository I wasn't really sure how I wanted
to do branching, tagging, etc. I took the route where each project
had its own tags, branches, and trunk directories and initially that
worked. What got me into a little trouble was that some of my
projects could be developed independently but when it comes to
releasing them the combination of them makes the release. These
individual projects will never be released by themselves.

So what I currently have is:

/project1/branches
/project1/tags
/project1/trunk

/project2/branches
/project2/tags
/project2/trunk

etc.

What I'd like to have is:

/project/branches/...
/project/tags/release_1_0_0/subproj1
/project/tags/release_1_0_0/subproj2
/project/tags/release_1_0_0/subproj3
/project/tags/release_1_3_7/subproj1
/project/tags/release_1_3_7/subproj2
/project/tags/release_1_3_7/subproj3
/project/trunk/subproj1
/project/trunk/subproj2
/project/trunk/subproj3

So now to my questions:

1. What is the best way to migrate my repository to this new structure?

2. How do I go about getting developers to migrate to this new structure?

Thanks in advance.

-- 
Warren Gavin
wmopnc@gmail.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org