Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

WTP 2014-11-20

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

  • Congratulations Victor on becoming JSDT project lead - Thanks Chris for your continued service.

WTP Calendar

(Weekly Google Calendar)


For Luna overall dates, see the Simultaneous Release Calendar


Release / Build status

WTP 3.6.3: Luna SR2

3.6.3 Schedule

11/20 M build smoke/declare
12/4 M build smoke/declare
Next build/smoke not until 1/8/2015?
  • Luna SR2 GA: 2/27/2015

3.6.3 Builds

WTP 3.7.0: Mars

3.7.0 Schedule

Mars M3 11/14
12/4 I build smoke/declare
12/11 special I build smoke/declare - M4 candidate
Mars M4 12/19
Next build/smoke not until 1/8/2015?
Mars M5 2/6/2015

3.7.0 Builds

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.6.3
Mars targeted bugs

Blockers, Hot-Bugs, Hot-Features

Blocker and Critical
Hotbugs [1]
Hotfeatures [2]
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

We'd like to make a try to integrate into JSDT (WTP 3.7.x) some tools like npm, bower, nodejs, basing on Stéphane Bégaudeau's project (https://github.com/sbegaudeau/webtools.jsdt). I feel that most of JSDT changes as well as additional plugins could be proposed for review using Gerrit, as it can significantly simplify the review process. What is the best way to start such a process?

JavaServer Faces

Server Tools

  • This week: bug 450015
  • Next week: TBD

WTP Source Editing

We'd like to include the following issue into 3.7 release plan: https://bugs.eclipse.org/bugs/show_bug.cgi?id=448152 - [validation] Ability to ignore custom html tag (UI part that adds Validation Pref. page changes and new QuickFix) The core part (changes in the validator itself) was merged into 3.6.2 in https://bugs.eclipse.org/bugs/show_bug.cgi?id=444545

Web Services Tools

Releng

VJET

Any others?

Other business - Long term tracking items

  • Gerrit adoption
    • JavaEE team following JSDT / (Mickael's instructions) - will report on progress
    • Broad adoption requested to improve WTP's non-committer contributions
  • Proposal to merge EJB project into Java EE project
    • Preparing restructuring docs

References

  1. Hotbug Policy
  2. Hotfeature Policy

Also, see

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

Back to the top