WTP 2013-09-12

From Eclipsepedia

Revision as of 17:46, 11 September 2013 by Cbridgha.us.ibm.com (Talk | contribs)

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

  • Trying out a small format change to our status meetings
    • Release / Build status
    • Bug and feature requests (including Neil's old quality section)
    • Project scrum section - Each project answers: 1) What are working on? 2) Planning to work on in next week?

WTP Calendar

(Weekly Google Calendar)


For Kepler/Luna overall dates, see the Simultaneous Release Calendar


Release / Build status

WTP 3.5.1

3.5.1 schedule

9/12 Declared M-build (RC4) <== final build, if needed (still in +3 PMC mode)
September 13 - September 27 is "quiet" to allow in depth testing with no changes
9/27 Official Release


+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

WTP 3.6: Luna


3.6.0 Schedule

09/12 Normal Luna 3.6.0 Integration build
...
09/26 WTP M2 Candidate build
10/4 Official Luna 3.6.0 M2 availability

Luna Schedule(From Eclipse Luna Simultaneous_Release_Plan)

                                                              Elapsed Weeks  
      End Date                      Span from +0         for RC0   for EPP avail
M1  Friday, August 23, 2013           08/09 to 08/23          6         8   (from previous release GA)
M2  Friday, October 04                09/20 to 10/04          6         6   (from M1)
M3  Friday, November 15               11/01 to 11/15          6         6   (from M2)
M4  Friday, December 20               12/13 to 12/20          6         5   (from M3) (shift from 2 week window to 1 week window)
M5  Friday, January 31, 2014          01/24 to 01/31          6         6   (from M4) (plan to "lose" a week for end-of-year  holidays)
M6  Friday, March 14                  03/07 to 03/14          6         6   (from M5) 

EclipseCon! (03/17 to 03/20) 

M7  Friday, May 09                    05/02 to 05/09          8         8   (from M6) (extra week(s) for EclipseCon)
RC1 Friday, May 23                    05/16 to 05/23          2         2   (from M7)
RC2 Friday, May 30                    05/23 to 05/30          1         1   (from RC1)
RC3 Friday, June 06                   05/30 to 06/06          1         1   (from RC2)
RC4 Friday, June 13                   06/06 to 06/13          1         1   (from RC3)

Quiet week, June 16 to June 20
(no builds during "quiet week", assumed all code is done by end of RC4                         

Release Wednesday, June 25, 2014


See "references" [1] for detailed explanation of what these dates mean. See also the Overall Luna Schedule.

Bug and Feature Highlights

Focus on Quality

  • Improve:
  • Triage:
  • Target to a specific release or "future" if planning to fix but not in the next release
  • Adjust severity as appropriate

Release Bug Review

Bugs targeted to 3.5.1
Bugs targeted to 3.6

Blockers, Hot-Bugs, Hot-Features

Blocker and Critical
Hotbugs [2]
Hotfeatures [3]

Project scrum section

  • Each project answers
    • What are working on?
    • What are you planning for next week?

WTP Common Tools

Dali Java Persistence Tools

WTP EJB & Java EE Tools

  • Last week: Branched 3.5.1, pushed [414706][CBI]
  • Next week: Work on [Bug 417032] Deadlock due to Resource Listener waiting for workspace lock

JavaScript Development Tools

JavaServer Faces

Server Tools

WTP Source Editing

Web Services Tools

Any others?

Other business - Long term tracking items

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
  3. Hotfeature Policy

Also, see

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