Jump to: navigation, search

WTP 2011-05-19

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 updated through June, 2011)


For Indigo/Helios overall dates, see a Simultaneous Release Calendar


Focus on Quality (Neil)

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

WTP 3.2.4

  • Voting finished - ready to officially release 5/20 latest build


3.2.4 Schedule

5/20 WTP 3.2.4 GA

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

Bug Review

Bugs targeted to 3.2.4
Bugs targeted to (Dali) 2.3.4
PMC Review/Approval Summary

WTP 3.3.0

Schedule

RC2 05/19 (for delivery to Indigo+2 on 05/24) (after this build, begin PMC +2)
RC3 05/26 (for delivery to Indigo+2 on 05/31) (after this build, begin PMC +3)
RC4 06/02 (for delivery to Indigo+2 on 06/07) [Final build]
GA 06/22

Bug Review

Hotbugs [2]
Blocker and Critical
Bugs targeted to M7,RC1,RC2,3.3
Bugs targeted to (Dali) M7,RC1,RC2,3.0
Unfixed bugs targeted to the past -- please triage!
PMC Review/Approval Summary

Release Materials

  • IP Log submitted on 5/18 (i.e., on time)
  • Release documentation ... ready for Project Leads ... work can be tracked in bug 346496. Need to complete before next Thursday 5/26.

Reminders for extra testing

  • Using 4.1 as base, of our Indigo deliverables

Other business

  • Another maintenance release proposed: Several projects have requested another maintenance release on Helios, so the PMC has agreed it is feasible to have a 3.2.5 release.
Schedule to be proposed later. And we still need to workout how to balance multiple streams
(i.e. we don't ask everyone to test every week each of the three: Helios maintenance, Indigo maintenance, and Juno maintenance. ...."
Committers must make sure the streams are cumlative ... that is, a fix going into Helios maintenance needs to go into Indigo maintenance which needs to go into Juno release
  • Reminder - check status for Babel maps for Indigo!

References

  1. 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.]
  2. Hotbug Policy

Also, see

Google Summer of Code and
Current 2011 Ideas
3.3 Rampdown plan
Standard Format Plans
WTP 3.2.x maintenance release plan
how/when to branch code?
IP Logs selector
WTP Helios retrospective.
See also the WTP Meeting Archive-Reference Page.