great news indeed!!!! thanks for sharing that...
Rusk, Patrick wrote:
>>The eclipse version control plugin support between M5 and M6
>>appears to be radically refactored. Radical meaning they agile
>>programmed it to death ;-) probably a good thing in the long
>>term but in the short term it is a fair bit of work. I suspect
>>that the differences between each eclipse M# version will
>>stabilize when 3.0 is released as a "Latest Release" build as
>>opposed to a 3.0 stream stable build. In essence the M# releases
>>are betas and it is difficult to keep up with the refactoring
>>joneses on the eclipse team.
>>
>>
>
> I suspect the API may be in stable shape now. Check out the
>following link from the Eclipse Web site (beware line wrap):
>
>http://www.eclipse.org/eclipse/development/eclipse_project_plan_3_0.html
>
>In particular, note this section:
>
>-------- cut --------
>
>Release milestones
>
>Release milestone occurring at roughly 6 week intervals exist to facilitate
>coarse-grained planning and staging. The milestones are:
>
>Friday June 6, 2003 - Milestone 1 (3.0 M1)
> - stable build reflecting progress
>Friday July 18, 2003 - Milestone 2 (3.0 M2)
> - stable build reflecting progress
>Friday August 29, 2003 - Milestone 3 (3.0 M3)
> - stable build reflecting progress
>Friday October 10, 2003 - Milestone 4 (3.0 M4)
> - stable build reflecting progress
>Friday November 21, 2003 - Milestone 5 (3.0 M5)
> - initial API freeze for breaking changes
> - stable build reflecting progress
>Friday December 19, 2003 - Milestone 6 (3.0 M6)
> - API freeze for breaking changes
> - stable build with focus on reducing the bug backlog and fixing
>memory leaks
>Friday February 13, 2004 - Milestone 7 (3.0 M7)
> - stable build reflecting progress
>Friday March 26, 2004 - Milestone 8 (3.0 M8)
> - stable build reflecting progress
>Friday May 7, 2004 - Milestone 9 (3.0 M9)
> - stable build
> - feature complete
> - development freeze
> - lock down and testing begins
>
>The 3.0 release is targeted for June 2004. All release deliverables will be
>available for download as soon as the release has been tested and validated
>in the target operating configurations listed below.
>
>-------- cut --------
>
>Apparently, M6 has an "API freeze for breaking changes". If that doesn't
>mean freezing the APIs for plug-ins, I don't know what would.
>
> While M5 was supposed to be an "initial API freeze", I'm guessing
>that the Eclipse project went through a lot of the last-minute "get those
>API changes in now or never" activity that "1.0-stabilization" on Subversion
>just saw.
>
> I seem to recall from something I read elsewhere on the Eclipse site
>that they're committed to freezing APIs well before the 3.0 release, so that
>tools relying on the APIs can release their 3.0 versions simultaneously.
>
> So, if I interpret this correctly, now would be a good time to put
>effort into the "subclipse-3" branch.
>
> And with excellent timing, it seems McClain has jumped into the fray
>and started checking stuff into the eclipse-3 branch today! (Wonderful think
>that "svn log -v" is!) Cedric and McClain are my heroes for doing this
>Subclipse work.
>
>Patrick Rusk
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
>For additional commands, e-mail: users-help@subclipse.tigris.org
>
>
>
Received on Fri Jan 30 10:03:26 2004