WTP 2013-01-31

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 - 135, last week - 136)

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

Triage:

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

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

WTP 3.4.2

3.4.2 Schedule

1/31 RC3 build (after this build, begin PMC-review ramp-down (+3 begins))

2/07 final M build (with one week of buffer following this week, quiet week, until 2/22 (re-spin would require +3))

2/22/2013 Juno SR2 GA

Bug Review

Bugs targeted to 3.4.2

Hotbugs

Blocker and Critical

WTP 3.5: Kepler!

Smoke Test Results
Kepler planning - Top Level Plan
- Plan requirements....
- Platform Kepler release requirement document approved

3.5.0 Schedule

01/31 M5 candidate build declare

02/08 Official Kepler 3.5.0 M5 availability - no declare

...

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

Ongoing GIT discussion
- Discuss Git workflows, best practices, project standards(versioning) experiences etc...
- WTP Git Workflows
- Git education wiki page

Anything else?
- Question about handling validation after plugin has stopped.

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