Skip to main content
Jump to: navigation, search

WTP 2013-08-01

Revision as of 13:27, 1 August 2013 by (Talk | contribs) (3.6.0 Schedule)

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.5: Kepler

  • Retrospective postponed to later this month when most folks are around to contribute

WTP 3.6: Luna

3.6.0 Schedule

08/01 Regular I Build declare


08/15 WTP M1 I Build declare
08/23 Official Luna 3.6.0 M1 availability - no declare


10/4 Official Luna 3.6.0 M2 availability

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

WTP 3.5.1

  • Aligned with Eclipse Kepler SR1 Schedule
  • Builds started - junits need attention(move to jre7 build machines)
  • No declared builds until 7/25
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

  • CBI -
    • Thanh has done an excellent job nudging us along, and we all need to be responsive to the requests.
    • latest blocker bug
    • Eclipse Common Build Infrastructure home
    • Very useful Retrospective on platform move
      • "We still have monolithic build. Apparently would take a LOT of work to change that. This surprised some of us."
      • "Surprised that the time to do (a clean) Tycho/Maven build is about the same as for (a clean) PDE Build. (2 to 3 hours for Platform builds, using either technology ... about an hour spent signing in either case). "


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