Re: [wtp-pmc] Plan for moving to M3 based builds?

[Arthur Ryman <ryman@xxxxxxxxxx>]

David,

I believe we did discuss this topic
and agreed to wait until M9 to start 3.2 builds. When we run into breakage
caused by dependence on internal code we should fix them if possible on
the 3.1 stream (in the case API exists). Failing that, we'll have to split
stream and create a 3.2 branch, but we should defer as long as possible
to avoid getting distracted from our 1.0 delivery. 

Arthur Ryman,
IBM Software Group, Rational Division

blog: http://ryman.eclipsedevelopersjournal.com/
phone: +1-905-413-3077, TL 969-3077
assistant: +1-905-413-2411, TL 969-2411
fax: +1-905-413-4920, TL 969-4920
mobile: +1-416-939-5063, text: 4169395063@xxxxxxx

David M Williams <david_williams@xxxxxxxxxx>
Sent by: wtp-pmc-bounces@xxxxxxxxxxx

10/18/2005 02:25 AM

Please respond to
"WTP PMC communications (including coordination, announcements,  and Group discussions)"

To	wtp-pmc@xxxxxxxxxxx
cc
Subject	[wtp-pmc] Plan for moving to M3 based builds?

I think Jeffrey reminded us we didn't even have a plan for when to move
to M3 (Eclipse 3.2) based builds, 
(And in fact, Tim might have tried too last week, but I'm not sure we let
him finish. :) 

And, I think we have in fact had such a plan, just not very public, and
not very crisp. So, let's chrunch on following, and see 
if it tastes right. 


>From previous Note from Tim W.: 

11/4/2005       M3      +1    
 +2      WTP/TPTP/BIRT join train

Which means we, WTP, would "join the train" on 11/18.


Funny, but our WTP M9 is 11/18 :)  I'd like to recommend we begin
M3-based 
builds on 11/21, thus having our first M3 based I-build
on Friday, 11/25 (allowing the usual 1 week of warm up, even though there's
two day's of holidays for us here in U.S.). 

While we will be VERY busy with the final stages of Release 1,
I think that'd give us some time and some hope to fix any easy and obvious
bugs with base M3 by the 
time we release 1.0 (for 3.1.1.) on 12/15. 

12/16 is the time base M4 comes out, so that should also make our adoption
of M4 less painful, and would be nice to have some statement "that
only moderatly 
tested, but our 1.0" works on M3". 

Of course, none of this official "join-the-train-via-builds"
rules out individual 
developers or community taking an "early" look, pulling our code
into 
an M2 based environment, and fixing things or making changes so that 
things are compatible for both 3.1.1 and 3.2 stream -- but, so far, know
of 
no need to produce a build prior to 11/25. Guess that would be our
"Thanksgiving milestone" ... if that's not too "American"
:) 

Any thoughts? I'm assuming this is still plan for Eclipse Train. 

Thanks_______________________________________________
wtp-pmc mailing list
wtp-pmc@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-pmc