Jump to: navigation, search

WTP 2014-05-01

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

Please use the same phone number as usual, but use Participant Code: 32557235 for today's status meeting.

USA Toll-Free: 888-426-6840 USA Caller Paid: 215-861-6239 For Other Countries: https://www.teleconference.att.com/servlet/glbAccess?process=1&accessCode=5019600&accessNumber=2158616239 Participant Code: 32557235

WTP Calendar

(Weekly Google Calendar)


For Luna overall dates, see the Simultaneous Release Calendar


Release / Build status

WTP 3.6: Luna


3.6.0 Schedule

M7 05/02 (for delivery to Luna+2 on 05/06)(after this build, begin PMC +1)
RC1 05/16 (for delivery to Luna+2 on 05/20)(after this build, still PMC +1)
RC2 05/23 (for delivery to Luna+2 on 05/27)(after this build, begin PMC +2)
RC3 05/30 (for delivery to Luna+2 on 06/03)(after this build, begin PMC +3)
RC4 06/06 (for delivery to Luna+2 on 06/10) [Final build]
Luna GA 06/26

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 WTP Luna

Blockers, Hot-Bugs, Hot-Features

Blocker and Critical
Hotbugs [2]
Hotfeatures [3]
Hotfeatures - triaged with helpwanted

Project scrum section

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

WTP Common Tools

Dali Java Persistence Tools

WTP EJB & Java EE Tools

JavaScript Development Tools

JavaServer Faces

  • This week: Feature License, CBI Test failure
  • Next week: CBI

Server Tools

  • This week: Fixed bug 431970, 432580 and 432788
  • Next week: bug 433928

WTP Source Editing

Web Services Tools

  • This week: not much
  • Next week: 433929- Update the Web Services license features to 1.0.1 for Luna

Releng

  • This week: Opened bug 433700 to address the Eclipse license update issue, updated build prereqs
  • Next week: Declare M7
  • Found workarounds for some build issues by setting "org.eclipse.sdk.ide" or "org.eclipse.jst.enterprise_sdk.feature" as dependencies. Not ideal but gets us moving forward if there is no time to investigate more specific dependencies.

VJET

Any others?

Other business - Long term tracking items

  • Historically - WTP hasn't published an endgame "plan" - but this Endgame plan from the platform is a good reminder of testing/planning activities that is appropriate for your projects.
  • Time to review Help documentation - We were late publishing last year, with almost no updates. - We will publish on time this year, and should update stale, outdated content. - Please review.

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