Jump to: navigation, search

Difference between revisions of "WTP 2013-05-16"

(WTP 3.5: Kepler)
(WTP 3.5: Kepler)
Line 36: Line 36:
* Kepler planning - [http://www.eclipse.org/projects/project-plan.php?planurl=http://www.eclipse.org/webtools/standard-project-plans/kepler/wtp-plan.xml Top Level Plan]
* Kepler planning - [http://www.eclipse.org/projects/project-plan.php?planurl=http://www.eclipse.org/webtools/standard-project-plans/kepler/wtp-plan.xml Top Level Plan]
** [[WTP_3.5_Ramp_down_Plan_for_Kepler| Ramp down plan for Kepler]]
** [[WTP_3.5_Ramp_down_Plan_for_Kepler| Ramp down plan for Kepler]]
** [http://www.eclipse.org/webtools/plans/3.5.0RC1/pmc-bug-approval.php PMC approved bugs]

Revision as of 11:00, 16 May 2013

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

3.5.0 Schedule

RC1 05/16 (for delivery to Kepler+2 on 05/21)(after this build, still PMC +1)
RC2 05/23 (for delivery to Kepler+2 on 05/28)(after this build, begin PMC +2)
RC3 05/30 (for delivery to Kepler+2 on 06/04)(after this build, begin PMC +3)
RC4 06/06 (for delivery to Kepler+2 on 06/11) [Final build]
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 - Long term tracking items

  • JavaScript Editor with NJSDoc contribution
    • Opened this bug to investigate this contribution


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