Skip to main content
Jump to: navigation, search

WTP 2009-05-14

WTP Development Status Meeting


Project Leads
Keith Y
Nitin Y
Kaloyan Y
Raghu Y
Neil Y
David Y
Carl Y
Dave R
Angel Y
Valentin Y
Nick Y
Gabriel Y
Chris Y

Note: feel free to correct any errors/omissions in above attendance record.

Announcements And Special Reports

  • We (PMC) have decided to submit one set of review materials for 3.1 Review.
So no need to press "submit" after you fix up Project level IP logs
PLs will still need to provide input/sections
Due 5/29 ... I'll get drafts started within the week.

WTP Calendar

Focus on Quality (Neil) - On hold for now

  • Focus Item:
  • Upcoming Focus item
  • Past Focus Items
  • Target to a specific release or "future" if planning to fix but not in the next release
  • Adjust severity as appropriate
  • Mark invalid patches as obsolete
  • Target bugs to a release or "future" if not a current release
  • Target to a specific release or "future" if planning to fix but not in the next release
  • Adjust severity as appropriate

WTP 3.0.5

  • Ready to declare 3.0.5 RC2?
May 14, 2009 >= M-3.0.5-20090514023324

3.0.5 schedule:

April 10 - M build
April 24 - M build
May 8 - RC1
All changes after May 8 require PMC approval (1 vote)
May 15 - RC2
All changes after May 15 require PMC approval (2 votes)
May 22 - final build
May 29 - 3.0.5 GA

WTP 3.1

  • RC1 due next Tuesday!
  • We'll start a weekly Monday/Tuesday rhythm for 3.1 RC rampdown
  • PMC Review has started.
  • Bug Triage
There are still approximately 7 bugs targeted to M7?!
All open 3.1 bugs(table)

Let's review:

Project Plans

and ...

Konstantin volunteered to pursue questions with EMO on how to treat the people who are not current committers, but for which cvs shows some code touching.

and he did, see wtp-dev list message for details (but usually, not an issue that requires action).

Project Leads please update "automatic" IP Logs. See Development_Resources/Automatic IP Log


Ramp down

Reference our ramp down plan and policies

Should we participate in RC2? Ans: Yes (but expect to be pretty small, since 25th is U.S. Holiday)


Our initial schedule was based on Platform's proposed schedule.

The official "must do" schedule is the +2 category in the Galileo Simultaneous Release.

Normally, our milestone are one week after the Platform's delivery. Exceptions noted below.

3.0.1 Early Maintenance Release Aug 15
M1 -> Aug 22 (extra week added so not to overlap maintenance release)
3.0.2 Coordinated Maintenance Release Sep 24
M2 -> Sept 26 (extra week added so not to overlap maintenance release) (updated)
M3 -> Nov 7 (short milestone, since "making up" for added week above)
3.0.3 Early Maintenance Release Nov 14
M4 -> Dec 19
M5 -> Feb 6
3.0.4 Coordinated Maintenance Release Feb 25
M6 -> Wednesday, March 18 Feature Complete, API Freeze, UI Freeze, NLS, Accessibility
(EclipseCon March 23-27)
M7 -> Tuesday, May 5 Performance tuning, documentation, bug fixing
RC1 -> Tuesday, May 19 Serious bugs only, focus on stability.
RC2 -> Tuesday, May 26 Serious bugs only, focus on stability.
RC3 -> Tuesday, June 2 Very serious bugs only.
RC4 -> Tuesday, June 9 Very very serious bugs only.
RC5 -> Tuesday, June 16 Hopefully no changes from RC4. Prepare web pages, update sites, etc.
GA -> Wednesday, June 24

Other business

Bob Fraser and Nova the look and feel: (see bug 261721)

Bob reported about ready, but will be a few weeks, since he'll be out a week. There was some discussion of what to delete from website (e.g. delete phoenix and nova prototype pages).


See also the WTP Meeting Archive-Reference Page.

Back to the top