[wtp-dev] Copies of pre-req'd I-builds (was: Our march to M4)

[David M Williams <david_williams@xxxxxxxxxx>]

Yes, agreed. And, to publicly remind
everyone :) Naci and his "build team" have offered 
to handle this in the build scripts
(and I am assuming he'll keep us all updated on progress). 

It turns out EMF has no plans to ever
produce "M builds" per se, (but I know Jeffrey Liu is 
working behind the scenes to at least
get them to mark some as 'stable', which would 
mean they would be left on download
page. (but, until they agree and change process, 
we still need to keep a copy). 

VE/JEM has some plans to produce M builds
eventually, but their schedule is a bit off the normal pattern,
so this is the best we can do (and JEM
is very stable, so no risk there, just a naming/process issue). 

We get spoiled by that great GEF team
who so regularly produce stable builds in synch with the rest of Eclipse

(and, for those that don't know me and
my sense of humor ... I'm not exactly an unbiased observer of GEF :)

David

Arthur Ryman <ryman@xxxxxxxxxx>
Sent by: wtp-dev-bounces@xxxxxxxxxxx

04/15/2005 04:12 PM

Please respond to
"General discussion of project-wide or architectural issues."

To	"General discussion of project-wide or architectural issues." <wtp-dev@xxxxxxxxxxx>
cc
Subject	Re: [wtp-dev] Our march to M4

David, 

If we are using I-builds of EMF and JEM for M4, then we really should make
local copies of them on our download server to avoid broken links a few
months from now. 

Arthur Ryman,
Rational Desktop Tools Development

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
intranet: http://labweb.torolab.ibm.com/DRY6/

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

04/15/2005 12:55 PM

Please respond to
"General discussion of project-wide or architectural issues."

To	wtp-dev@xxxxxxxxxxx
cc
Subject	[wtp-dev] Our march to M4

Given our status, plans and goals for M4, there's the general plan for
builds/testing for the next little while. 

The main goal is to have a Milestone quality build by Tuesday morning so
we, and community, can 
have several days to test for any show-stopping defects. 

We'll change cruise control to do "continuous" I-builds for the
next several days, following the usual 
schedule of 11 PM, 8:30 AM, and 3:30 PM (EDT).  And, please remember,
there's roughly a 15 minute 
lag between extssh commits and pserver fetches .. so commit/release early
! 

Teams with large renames/refactorings still to do should work directly
with effect teams, and plan a time 
that teams can respond before next scheduled I-build and all have a coordinated
"release" of changes, 
or I-build will fail miserably and do no one any good. 

Teams should "continuously" be picking up I-builds, sniff testing,
and making sure blocking/critical fixes. 
are resolved. 

>From talking to EMF and JEM team leads, the version of EMF we should
use for this milestone 
is 
EMF I20050414117 
we'll try and get that in today's 3:30 build. 

and JEM I20050415xxxx, to be created later today, 
we'll get that in Saturday's builds. 

(no substantial changes are expected, but we should use a coordinated "stable"
version 
to be reproducible and to report bugs against ... both these teams say
they are not really 
producing "M" builds of these packages, but these are based on
M6, and JEM will be based on 0414 EMF. 

I believe the GEF pre-req has already been fixed, and will be in today's
3:30 build. 

Naci or Ozgur .. can you check if we can capture and upload "console
log" from JUnit tests .... 
that might be helpful is detecting problems. 

Thanks all. 
_______________________________________________
wtp-dev mailing list
wtp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-dev
_______________________________________________
wtp-dev mailing list
wtp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-dev