Skip to main content
Jump to: navigation, search

WTP 2011-09-01

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, 2012)

For Juno/Indigo overall dates, see the 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.5

  • Projects should notify Chuck / Carl if it is known week to week they will not be participating, so smoke report template can be changed

3.2.5 Schedule

9/2 M build
9/9 M build
9/16 M build - all teams start smoke testing
9/23 M build
9/30 M build
10/7 M build (after this build, begin PMC-review ramp-down (+1 begins))
10/14 M build (after this build, begin +2)
10/21 M build (after this build, begin +3)
10/28 M build final build (with one week of buffer following this week, quiet week, until 11/4 (re-spin would require +3))
11/4 WTP 3.2.5 GA

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

3.2.5 Bug Review

Bugs targeted to 3.2.5

WTP 3.3.1

  • PMC review +2 next week (after we declare)

3.3.1 Schedule

8/26 M build (after this build, begin PMC-review ramp-down (+1 begins))
9/2 M build (after this build, begin +2)
9/9 M build (after this build, begin +3)
9/16 final M build (with one week of buffer following this week, quiet week, until 9/23 (re-spin would require +3))
9/23 SR1 GA

Bug Review

Bugs targeted to 3.3.1
Hotbugs [2]
Blocker and Critical

WTP 3.4.0

  • latest build
  • Discuss 3.4 default base moving to 4.2. What problems remain? Carl to mention progress publishing 4.2 based builds. Move smoke testing to 4.2 - Can we achieve goal of delivering M2 driver on 4.2?
  • While we are on the subject of Juno... Time to get serious about planning:
    • Project Leads: Please fix the 'project plan url' field in the Project Meta-data to point to Juno. (HowTo)
    • Project planning schedule:
      • First draft : 09/30 (M2 Milestone)

3.4.0 Schedule

9/02 I build declare
9/09 I build declare
9/16 I build declare
9/23 M2 declare
9/30 Official WTP 3.4.0 M2 availability - no declare

Bug Review

Bugs targeted to 3.4.0
Blocker and Critical

Other business

  • Any other topics?

Indigo release retrospective


  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

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.

Back to the top