Skip to main content
Jump to: navigation, search

WTP 2012-08-23

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

Git Builds delivered to Juno SR1 RC1 and Kepler M1!

WTP Calendar

(Weekly Google Calendar updated through June, 2012 - Yes I need to update!!)

For Juno 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 Moving to GIT!

WTP 3.4.1

  • No build declare this week
  • RC2 Candidate build next week
  • PMC +1 required for all commits
  • Work on those versioning issues!!

3.4.1 Schedule

8/16 RC1 build (after this build, begin PMC-review ramp-down (+1 begins))
8/30 RC2 build (after this build, begin PMC-review ramp-down (+2 begins))
9/6 RC3 build (after this build, begin PMC-review ramp-down (+3 begins))
9/13 final M build (with one week of buffer following this week, quiet week, until 9/28 (re-spin would require +3))
9/28 Juno SR1 GA

Bug Review

Bugs targeted to 3.4.1
Blocker and Critical

WTP 3.5.0 Kepler!

  • Build coming friday.... Release your changes!
  • EMF Validation, among others not in Kepler yet... may delay our inclusion in release train
  • Start planning - Top Level Plan

3.5.0 Schedule

8/24 Official Kepler 3.5.0 M1 availability - no declare
8/31 First M2 I build declare


10/05 Official Kepler 3.5.0 M2 availability - no declare
11/16 Official Kepler 3.5.0 M3 availability - no declare
12/21 Official Kepler 3.5.0 M4 availability - no 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.0
Hotbugs [2]
Blocker and Critical

Other business

  • Tomorrow - Sending note to wtp-dev, and posting to wtp community forum to ask for feedback, improvements, general requests...
  • All project leads should update project metadata (bugzilla targets, release info, Kepler?)
  • Anything else?


  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

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

Back to the top