Re: [imp-dev] Proposed reorg of IMP SVN repository structure

[Jurgen Vinju <jurgen@xxxxxxxxx>]

Hi,

I think this is a bad idea. 
  1) It deviates from the 'standard' idiomatic use of subversion, such that:
         a) newcomers will be surprised more than they are now.
         b) Team plugins for Eclipse may have trouble dealing with it
  2) It hampers independent development, release and deployment cycles for different parts of IMP:
         a) as IMP becomes larger, you will want to start releasing parts of it independently. This will not be 
             possible without tagging all projects in one go with the same tag. The tag would be meaningless for
             most of the code, but that would be a hard thing to trace.
         b) as IMP becomes larger and more people develop on it, you will want to branch different parts of the code.
             this will not be possible without branching all of the code, which is not a good thing for obvious reasons.
         b) It also projects a big blob architecture, where everything depends on everything eventually,
             which is not the case at all and should never be.

If convenience is really the only issue, then I guess we should wait a bit until the team plugins that have support
for the trunk/branches/tags idiom for subversion stabilize. It really is an interaction design issue for those tools. You should
be able to select a group of projects and check out their trunks in one go. Maybe we could suggest this as a feature, if
that has not already been done.

Another thing: aren't the "team project sets" capable of doing this checkout out of different projects in one go correctly by now?

Cheers,

Jurgen

On Thu, Apr 9, 2009 at 11:15 PM, Robert M. Fuhrer <rfuhrer@xxxxxxxxxxxxxx> wrote:

Hi Folks,

I'd like to reorganize the SVN repository structure. Right now, it looks like this:

 org.eclipse.imp
     proj1
         branches
         tags
         trunk
     proj2
         branches
         tags
         trunk
     ...
     projN
         branches
         tags
         trunk

It seems more conventional (and easier to deal with) for it to look instead like this:

 org.eclipse.imp
     branches
         proj1
         proj2
         ...
         projN
     tags
         proj1
         proj2
         ...
         projN
     trunk
         proj1
         proj2
         ...
         projN

This way, for the most common case (checking out trunk or a set of projects with a given tag/branch), one has a better chance of being able to select a contiguous set of projects, rather than having to expand each one in order to find the appropriate trunk/tag/branch.

Obviously this will cause short-term pain as we all rebuild our workspaces, but I think in the long run it will cause less confusion to newcomers and less manual work for veterans.

Comments?

--
Cheers,
 - Bob
-------------------------------------------------
Robert M. Fuhrer
Research Staff Member
Programming Technologies Dept.
IBM T.J. Watson Research Center

IMP Project Lead (http://www.eclipse.org/imp)
X10: Productivity for High-Performance Parallel Programming (http://x10.sf.net)

_______________________________________________
imp-dev mailing list
imp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/imp-dev