WTP 2013-06-20

From Eclipsepedia

Jump to: navigation, search

Contents

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

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

WTP 3.5.1

  • Aligned with Eclipse Kepler SR1 Schedule
  • Build will start immediately after we GA Kepler
  • No declared builds until mid July.
+0
Fri.
+1
Mon.
+2
Tues.
+3
Wed.
EPP
Thur.
Available
Fri.
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

Other business - Long term tracking items

  • Request from Ian for WTP Kepler articles...
    • Would the WTP project be interested in doing a series of Eclipse and Java EE 7 articles that we would use for the next Eclipse newsletter in July. Each month **we publish a newsletter to over 40K subscribers. The newsletter is usually focused on a specific topic so I was thinking ‘Support for Java EE 7’ might be a good topic.
    • You can see previous newsletters at http://www.eclipse.org/community/eclipse_newsletter/
    • We would need to have 3 articles to support the Java EE 7 topic. You can use existing articles that have already been written or new content. We would need the articles by July 19.


References

  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.