Jump to: navigation, search

WTP 2012-10-18

Revision as of 12:56, 18 October 2012 by Neil.hauge.oracle.com (Talk | contribs) (Focus on Quality (Neil))

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

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

  • Committer voting has concluded for Rosendo Martinez joining the wtp releng team with 3 + votes and rest sustaining. PMC approval needed.

WTP Calendar

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

For Juno/Kepler 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.4.2

3.4.2 Schedule

10/18 Weekly maintenance driver smoke and declare
2/22/2013 Juno SR2 GA

Bug Review

Bugs targeted to 3.4.2
Blocker and Critical

WTP 3.5: Kepler!

3.5.0 Schedule

10/18 Weekly integration driver smoke and 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
Hotbugs [2]
Blocker and Critical

Other business

WTP Website moving to GIT!

  • Review and prepare for all CVS website content to be migrated to Git - will open webmaster bug to move today!

Ongoing GIT discussion

  • 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.