Skip to main content
Jump to: navigation, search

WTP 2013-09-05

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 Kepler/Luna overall dates, see the Simultaneous Release Calendar

Focus on Quality (Neil)

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

WTP 3.6: Luna

3.6.0 Schedule

09/05 Normal Luna 3.6.0 Integration build
10/4 Official Luna 3.6.0 M2 availability

See "references" [1] for detailed explanation of what these dates mean. See also the Overall Luna Schedule.

WTP 3.5.1

3.5.1 schedule

9/5 Declared M-build (RC3) <== final build, unless blockers found
PMC +3 review: September 6 - 27(GA)
9/12 Declared M-build (RC4) <== final build, if needed
September 13 - September 27 is "quiet" to allow in depth testing with no changes
9/27 Official Release

RC1 (Warmup) 8/16 8/19 8/20 8/21 8/22 8/23
RC2 8/30 9/02 9/03 9/04 9/05 9/06
RC3 9/06 9/09 9/10 9/11 9/12 9/13
RC4 9/13 9/16 9/17 9/18 9/19 9/20
Juno SR1 ("GA") quiet: 9/20 quiet: 9/23 quiet: 9/24 quiet: 9/25 quiet: 9/26 GA: 9/27

Bug Review

Bugs targeted to 3.5.1
Hotbugs [2]
Blocker and Critical

Other business - Long term tracking items

  • Kepler retrospective follow-up
    • More communication desired between development teams and adopters(socializing plans etc)....
    • Advertising most wanted features - identify gaps - resources etc...


  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

Kepler SR1 Simultaneous Release Schedule
Indigo release retrospective
Standard Format Plans
WTP 3.5.x maintenance release plan
how/when to branch code?
IP Logs selector
See also the WTP Meeting Archive-Reference Page.

Back to the top