WTP 2013-04-04

WTP Development Status Meeting

Remember, any committer can add an agenda item. Typically, short announcements or news items go in the "Announcements" section at the beginning. Longer items or issues requiring discussion should go in the "Other business" section at end.

Announcements And Special Reports

WTP Calendar

(Weekly Google Calendar)

For Juno/Kepler overall dates, see the Simultaneous Release Calendar

Focus on Quality (Neil)

Improve:

Major or higher severity bugs by project (This week - 131, last week - 129)

Targeted to Future (candidates for severity downgrade?) (Total - 77, last week - 77)

Triage:

Untargeted bugs and enhancements with patches attached over 7 days old (This week - 71, Last week - 68)
Untargeted severity "Major" and higher bugs opened over 7 days ago (This week - 44, Last week - 40)
Options:

Target to a specific release or "future" if planning to fix but not in the next release
Adjust severity as appropriate

WTP 3.5: Kepler

Smoke Test Results
Kepler planning - Top Level Plan
- Ramp down plan for Kepler created

3.5.0 Schedule

04/04 Regular I build smoke / declare

04/11 Regular I build smoke / declare

04/18 Regular I build smoke / declare

04/25 Regular I build smoke / declare

M7 05/02 (for delivery to Kepler+2 on 05/07)(after this build, begin PMC +1)

RC1 05/16 (for delivery to Kepler+2 on 05/21)(after this build, still PMC +1)

RC2 05/23 (for delivery to Kepler+2 on 05/28)(after this build, begin PMC +2)

RC3 05/30 (for delivery to Kepler+2 on 06/04)(after this build, begin PMC +3)

RC4 06/06 (for delivery to Kepler+2 on 06/11) [Final build]

06/26 Kepler GA

See "references" ^[1] for detailed explanation of what these dates mean.

Bug Review

Bugs targeted to 3.5

Hotbugs ^[2]

Blocker and Critical

Other business

Google Summer of Code Ideas - http://wiki.eclipse.org/Google_Summer_of_Code_2013_Ideas

References

↑ Our plan dates are on 'Friday' of the week. But, we produce and test the build on Thursday of the week, and ideally declare on Thursday. The dates in the Google Web Tools group calendar are for 'Thursdays' since that's a calendar for committers. We give ourselves the buffer to Friday, as our "public" date, that others can pick up our build, just in case a regression is found on Thursday and we have to respin and retest. [Technically, some might say, we still have till the following Tuesday or Wednesday for some "Simultaneous Release" due dates ... but it's hard to do much in that window, without disrupting everyone ... so we'll not use that buffer, except for the worst emergencies.]
↑ Hotbug Policy

Also, see