[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: [Subclipse-dev] Future of trunk vs. eclipse-proposal branch

From: Mark Phippard <markp_at_softlanding.com>
Date: 2006-07-06 18:01:41 CEST

"Martin Letenay" <mle@whitestein.com> wrote on 07/06/2006 11:54:04 AM:

> I intend to thoroughly review and cleanup the code and mainly the
javadocs,
> starting with clientAdapter.
> I've seen you started work on the new "eclipse-proposal" branches, so
I'll
> switch there too.
>
> What's the intention of that branch vs. trunk ?
> Are we going to maintain the trunk as main feature/bugfix development
line
> for upcoming 1.1 releases and eclipse-proposal branches for longer term
work
> ?
> Will the eclipse-proposal once "replace" the trunk ?

For the most part, we should just work on trunk. After all, there is a
very real possibility that our proposal will not be accepted, and/or that
the process could take a very long time. I do not intend to stop
producing Subclipse releases.

I primarily created the branch to test how well refactoring would let us
convert the names/structure to match the proposal. It worked pretty
easily. I did it all in a few hours and it all works. I'd like for Brock
or someone to potentially start working on the idea of converting the
adapter to an extension point, and the branch would be the place to do
that for now.

So if you have something useful to do, that is not specifically about the
eclipse proposal, I would do it in trunk. We can figure out what to do
with it all later.

Mark

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: dev-help@subclipse.tigris.org
Received on Thu Jul 6 18:01:58 2006

This is an archived mail posted to the Subclipse Dev mailing list.