[wtp-dev] Status and I-Build Procedure for 10/28

[David M Williams <david_williams@xxxxxxxxxx>]

I-Build Reminder

Just a reminder we've started a new
process for I-builds, in an effort to keep them high quality, but more
timely. 

We'll get this on the web eventually,
but for now, I've repeated it at the end of this note. 
Note too I've added a section to be
explicit about who exactly we need to hear from before 
promoting a build. Feel free to suggest
others for the "must hear" list ... currently just wanted 
to have something concrete to go by.


Its especially important to re-read
and follow since this week, I'll be out of the office during all the interesting
times, so Naci will 
be herding the I-build through to promotion.
 

= = = = =

Status

Since I won't be at status call this
week, here's a few items I would have covered. 

I think we're on track to have (at least)
WST portion of "fine grained" features by M9. 
As before you can check some status
of "head" (nightly) builds at 
http://download.eclipse.org/webtools/committers/

RDB and WSI have some model/view fixes
to make to make "real".  WSI says 
"probably real soon" ... haven't
heard yet from Der Ping yet if changes needed 
are feasible for M9. 

Still to do: 

SDK portion (my responsibility). 
User doc/dynamic help (some on going
discussions are occuring)

ISV Doc portion (your? responsibility)

We haven't discussed ISV Doc (JavaDoc
and "overviews") in a LONG time .. so, now's 
the time. According to our feature architecture,
we should be have seperate 
ISV docs for each main subsystem (see

http://www.eclipse.org/webtools/development/arch_and_design/subsystems/SubsystemsAndFeatures.html
if you don't know what I'm talking about.


We did have one scheme, that produced
one big ISV Doc ... but that'll no longer work for correct 
"componentization".  There's
various schems/plans that would work ... any volunteers to make concrete?

= = = = = 

Repeat of new I-build times and procedures


Thursday 2 AM (Eastern) (That's Wednesday night
for most!):
 
        All code for weekly I-build release by Thursday
2 AM
 
Thursday 5 AM (Eastern):
 
        Weekly I-build candidate ready
 
        Teams should "smoke test" the I-build
on "committers" area, be
        Thursday 7 PM, at latest.
 
        Blocking bugs found can be released, but should
have clear
        bugzilla, with post to wtp-releng "requesting
respin"
        (even though, for now, we'll leave it automatic,
please
        consider it a request).
 
Thursday 7 PM (Eastern).
 
        Note to wtp-releng confirming tested and "ok"
or "not ok".
        (the later requiring a bug, and "plan"
to get ready for re-spin).
 
 
Friday noon
 
        Any teams releasing code for blocking bugs,
must have verified
        all ok by Friday noon, and send confirmation
to wtp-releng.
 
        Weekly I-Build announced and promoted to "downloads"
area.


Teams we must hear affirmation from
(either team lead, or delegate). 
Any committer may "veto" an
I-build, and request 
a re-spin to pick up a fix for a blocking
problem, but 
if no vetos, we must still get positive
"go" notes 
from following (please post to wtp-releng
list)

Servers (Tim DeBoer). 
Web Services (Chris Brealy)
J2EE (Chuck Bridgham)
Editing (David Williams)
RDB (Der Ping)
= = = = = = = = = = = = = = = = = =
= = = = = = = = = = = = 

Thanks all,