[wtp-dev] Status of M9 candidate build

[David M Williams <david_williams@xxxxxxxxxx>]

Apologies for the slow builds ... but
(I think) we have under control now, with some "quick fixes"
we'll 
have to live with for R1 (since, to
fix completely, we'd have to change infrastructure/process a little more
.. but, as agreed, 
we've made good progress for R1 and
will evolve our "componentization" in R1.5). 


As for the compile breaks in 
http://download.eclipse.org/webtools/committers/drops/I-I200511151729-200511151729/

I've opened 
https://bugs.eclipse.org/bugs/show_bug.cgi?id=116481
for the real fix that's needed eventually,
but (I think) I've fixed as far as builds go. 

So now... please (re) inspect
builds ... this one, I-I200511151729-200511151729, 
and the next one (available around 5
PM (I think))  should be 
carefully inspected visually by teams
to be sure all the right plugins and source is 
included where you expect. 

Next step: all "new"
code (as listed in last weeks status meeting) must be in by tonight, 
and a "candidate M9 build"
produced by Wednesday AM. 

Sniff test Wednesday morning build,
report to mailing list by noon Wednesday (eastern) 
if there are blocking problems that
would require a re-spin. 

After that, I propose we turn off automatic
I-builds .. and only build upon request, 
for bugs listed/posted here to mailing
list. 

The PMC did approve this morning the
committer's proposal to move the 
M9 release date to 11/23 (Wednesday)
instead of 11/18 (Friday). 

So, we do have one week of testing and
bug fixes
before M9 release. As always, we'll
need to be selective in what we 
fix, so as to not destabilize.  

Our objective is to produce an M9 milestone
release that the community will 
be able to pick up, use, test, and provide
good feedback on, so any bad problems 
can be fixed before the R1 release,
and, even if not able to fix all known problems, 
we'll at least be able to get a good
overall picture of the quality and the readiness to 
release. 

Thanks all,