Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: for the plan.

Jump to: navigation, search

WTP 2009-10-08

Revision as of 19:12, 8 October 2009 by David (Talk | contribs) (Attendees)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

WTP Development Status Meeting


Project Leads
Keith Y
Nitin Y
Kaloyan Y
Neil Y
David Y
Carl Y
Chris Y
Angel Y
Valentin Y
Nick Y
Gabriel Y
Ian Y

Note: feel free to correct any errors/omissions in above attendance record.

Announcements And Special Reports


WTP Calendar

(Weekly Google Calendar updated through June, 2010)

For Galileo and Helios overall dates, see a Simultaneous Release Calendar

Quality Focus Items (Neil)

  • Focus Item:
  • Target to a specific release or "future" if planning to fix but not in the next release
  • Adjust severity as appropriate
  • Ongoing Focus Items:
  • Mark invalid patches as obsolete
  • Target bugs to a release or "future" if not a current release

WTP 3.1.x

Declared builds to resume in January.


See also the Galileo ramp down dates


01/08 M Build
01/15 M Build for SR2 RC1
01/29 M Build for SR2 RC2 (PMC Review starts following this build)
02/05 M Build for SR2 RC3 Can this be our final build?
02/12 R Build Final Build
(02/26 Galileo SR2) (WTP 3.1.2) (fourth Friday of February)

Galileo Maintenance Plan

See WTP_3.1.x_Maintenance for documentation of scope of maintenance and approvals required.

WTP 3.2

  • Bugs
Blocker and Critical


M3 11/06
M4 12/11
M5 01/29
M6 03/12
M7 04/30
RC1 05/14 (followed by weekly RCs, if needed)
Final WTP 3.2 build 06/10
(06/23 Helios Release)

Note: these (and 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 "Simultaneous Release" due date ... but it's hard to do much in that window, without disrupting everyone ... so we'd not use that buffer, except for the worst emergencies.]

WTP 3.2G

  • We have once-a-day Galileo-based WTP 3.2 builds. Same WTP code. Different pre-req Platform. The goal is to make sure our 3.2 stream is at least compatible with both Galileo and Helios. Or, if we can not literally achieve being compatible, we should document why not and at least understand it.
  • Any issues?
bug 155558

Other business

  •  ?


WTP 3.1 Post Mortem

ramp down plan and policies

See also the WTP Meeting Archive-Reference Page.

Back to the top