Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Archived » IMP » Reorganization of the IMP SVN repository on eclipse.org
Reorganization of the IMP SVN repository on eclipse.org [message #576463] Thu, 03 September 2009 19:00
Robert M. Fuhrer is currently offline Robert M. FuhrerFriend
Messages: 294
Registered: July 2009
Senior Member
Hi All,

For those that don't subscribe to the mailing list, we've reorganized
the repository structure to adhere to the common convention of having
trunk, tags, branches at the top level, and individual plugin projects
underneath that, rather than the other way around (as it was before).

I believe you should be able to continue to use your existing workspaces
as they are, but it might be better to rebuild from a fresh drop.

Here's the note I posted to the imp-dev mailing list. For more details
and subsequent follow-ups, see the mailing list archives.

============================================================ ===========

Hi Folks,

While warming up for the next release, I finally got around to
reorganizing the IMP SVN repository. The new organization should make
the most common case (checking out HEAD of a set of projects on the
trunk) much simpler, and aligns the repository with the conventional
structure used by other projects.

I believe you should be able to continue to use your existing
workspaces, but it might be sensible to start fresh to avoid confusion.

So, instead of:

svnroot/technology/org.eclipse.imp
plugin1
branches
tags
trunk
plugin2
branches
tags
trunk
...

the repository now looks like this:

svnroot/technology/org.eclipse.imp
branches
branch1 - most of these were IMP-wide branches
(e.g. "Eclipse-3_2")
plugin1
plugin2
...
branch2
plugin1
plugin2
...
...
tags
OLD
plugin1
tag1 - these were all per-plugin release
tags (e.g. "release-0.1.1")
tag2
plugin2
tag1
tag2
...
trunk
plugin1 - all of these are now adjacent (yay!)
plugin2
...

N.B.: The organization of the "tags" folder above reflects the fact that
the all of the existing tags were per-plugin, rather than per-feature or
IMP-wide. In other words, it didn't make sense to group the 0.1.1's (for
instance) together by putting the 0.1.1 at the top level of the "tags"
folder.

We now need to decide how to tag the projects on new releases.

I'm leaning toward tagging all of a feature's plugin projects with the
feature's version number.

Comments?

============================================================ ===========

--
Cheers,
-- Bob

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

IDE Meta-tooling Platform Project Lead (http://www.eclipse.org/imp)
X10: Productive High-Performance Parallel Programming (http://x10-lang.org)
Previous Topic:New release of IMP available on the update site
Next Topic:Reorganization of the IMP SVN repository on eclipse.org
Goto Forum:
  


Current Time: Mon Dec 22 16:20:55 GMT 2014

Powered by FUDForum. Page generated in 0.03381 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software