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.

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.

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.