SVN repository is a bit of a mess

Hi,

I've just been looking at using warp-persist, and whilst it seems like a
useful tool, the messy state of the svn repository makes it a bit of an
epic effort to understand the state of the project.

I would like to propose that it be tidied up.

First, I shall describe the current status as I have understood it from the
logs:

/branches: Empty.

/tags: All the tags contained here contain a spurious extra /warp-persist/
directory within them, which seems to be a relic of previous fighting with
svn. Personally I'd favour removing this extra directory level.

/tags/warp-persist-1.0 v.s. -1.0proper - this is a bit confusing. Assuming
that 1.0proper is what actually got released as jar files, perhaps the 1.0
tag should be renamed to warp-persist-1.0withdrawn or something clearly
negative?

/trunk/tags/warp-persist-HibJPA: An empty spurious directory which should
be removed.

/trunk/tags/warp-persistWithJpaAndHibernate: A tag of the latest state of
warp-persist-improper-branch. I suggest deleting it as it doesn't seem to
serve any purpose.

/trunk/warp-persist-improper-branch: Some old relic of a failed initial
import into svn, it seems. I would either delete it or move it to
/branches/obsolete-improper-initial-import.

/trunk/warp-persist: The project's actual trunk, which I would highly
recommend relocating to /trunk.

Please let me know how you feel about all the above, and if desired I will
be more than happy to supply a scripted sequence of svn mv and svn rm
commands to effect the reorganization in as tidy a form as possible.

Original issue reported on code.google.com by m...@j.maxb.eu on 17 Aug 2009 at 6:09

wangscript / warp-persist

SVN repository is a bit of a mess #33