Sorry for not waiting, but I had the time and bandwidth and wanted to get
this done so that we do not have to scramble to do it later when there
is a problem. This is what I have done:
1) Created an eclipse2.x branch and populated it with the Subclipse and
svnClientAdapter code that corresponds to Subclipse 0.9.3.1 (our last
build for Eclipse 2.x). If someone wants to tweak this version, this will
make it easier to do.
2) Copied the projects from the subclipse-3 branch to trunk. We should
now be using trunk for all of our main development!! Use the switch
option
to move your WC to the trunk version of the project.
3) Copied svnClientAdapter from trunk to subclipse-3 branch so that it
will be easy to do additional builds/releases for that line if we need or
want to.
This is where this leaves us:
* Eclipse 2.x development:
http://svn.collab.net/repos/subclipse/branches/eclipse2.x
Not happening, but if it did, it should go on the eclipse2.x branch.
* Eclipse 3.x for Subversion 1.2.x
http://svn.collab.net/repos/subclipse/trunk/subclipse
This will happen on trunk. I suspect that this is where most if not
all
development activty will happen and where future releases will be
created from. If it is at all possible, we will make this version also
support Subversion 1.1.x.
* Eclipse 3.x for Subversion 1.1.x
http://svn.collab.net/repos/subclipse/branches/subclipse-3
This will happen on the subclipse-3 branch, assuming that trunk becomes
incompatible with Subversion 1.1.x. If I see any commits to this
branch
in the next week or so, I will make sure that was the intention and
port
the changes to trunk if needed. If we need to do new releases, they can
just be version 0.9.30.2 etc.... We will use even numbers so that
JavaSVN can increment by one and use the odd number. I probably will
only roll new releases for dataloss bugs like the revert problem I
fixed
in the 0.9.30 release. Others are free to step in and do releases if
they choose. I will be glad to help.
I will be doing the majority of my work on trunk now.
Thanks
Mark
_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.
_____________________________________________________________________________
Received on Wed Apr 13 04:05:26 2005