Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[wtp-dev] Minutes of the WTP Status Telecon, 2006-06-01

See WTP Status Telecons [1] for more information.



Amy Wu

Arthur Ryman
Chris Brealey
Chuck Bridgham

Craig Salter
David Williams

Der Ping Chou
Jeffrey Liu
John Lanuti

Kate Price
Kathy Chan

Keith Chong
Konstantin Komissarchik
Larry Dunnell

Larry Issac
Lawrence Mandel

Nitin Dahyabhai

Raghu Srinivasan
Ted Bashor

Tim Deboer
Thomas Yip
Tim Wagner

1. WTP 1.5 Status

WTP 1.5 milestones plan [1]
Wednesday, 31-May-06
Component lead approval and wtp-dev notification required for all checkins
WTP Freeze
Wednesday, 14-June-06
WTP "cooldown" begins; only PMC-approved (ship-stopping) issues addressed hereafter
Tuesday, 20-Jun-06
WTP release candidate; platform-level triage (PMC approves changes with downstream consumer sign off)
Wednesday, 28-Jun-06
Gold master
Friday, 30-Jun-06
Callisto GA (WTP 1.5 GA Release, English only)


Important: From now on, use the target milestone field to indicate what you intend to fix in the 1.5 release. Bugs that we intend to fix in 1.5 should be targeted to 1.5 RC5. Others should be deferred. We don't want anything targeted to RC6 unless it is truely truely stop ship and we cannot fix it in RC5. Bugs targeted to RC5 should have a P1 or P2 priority.

Arthur - Let's go around the table to see what we are intending to fix for each component.

Tim - Have a few open bugs that look ugly. Will investigate and may ask for approval for this release, but they are not stop ships.

Chris - Have 19 open bugs. Target to fix them by the next couple weeks.

Craig - Have 8 bugs that we want to fix. Comfortable fixing them before code freeze

Chuck - We have 28 targetted to 1.5. 7 or 8 have requested for PMC approval. 9 of them are P3. The rest we feel comfortable getting them in before code freeze.

David - Have 5 or 6 for RC5 and others that will investigate and can be defered.

Der Ping - Will target bugs according to the process. No estimate on how many bugs RDB wants to fix at this moment.

1.1 WTP 1.5 Build Status - David Williams

David - RC4 is declared, it's available on the update site. For next week, 1.0.3, code in by Monday, smoke test by Tuesday and declare on Wednesday. For 1.5, code in by Wednesday, smoke test on Thursday and declare on Friday.

David - Please complete updating plug-in version numbers by this week.

David - There's a tool available to help you update version numbers, but it only works if the current plug-in version is accurate. Will investigate the tool.

Kathy - Will you handle the feature version numbers?

David - Yes, they are completed.

1.2 Bugs Waiting for PMC Approval [1] - Jeffrey Liu


Arthur - All bugs need to have a patch, well tested and safe.

Arthur - When you accept patches from contributors, make sure you update the IP log.

Tim W - Send me an email if you need more information on how to update the IP log.

Arthur - There will be meetings at 3:00 pm EST each day for PMC members to approve bugs. You can bring both 1.5 and 1.0.3 bugs to the meeting. Attendant is optional. This will start next Monday.

1.3 WTP 1.5 Hot Bugs [1] - Jeffrey Liu


1.4 WTP 1.5 Hot Bug Requests [1] - Jeffrey Liu

Owners should update the bug status
prior to the status telecon.


1.5 P1 Bugs [1] - Jeffrey Liu

1.6 P2 Bugs [2] - Jeffrey Liu"">

1.7 Blocking Bugs [1] - Jeffrey Liu

1.8 Critical and Major Bugs [1] - Jeffrey Liu"">

1.9 Bugs to be Triaged [1] - Jeffrey Liu

QA owners should triage these bugs.


1.10 Bugs Targeted to Past Milestones/Release Candidates [1] - Jeffrey Liu

There are currently bugs targeted to 1.5 M4, 1.5 M5, 1.5 M6, 1.5 RC1, 1.5 RC2, 1.5 RC3 and 1.5 RC4. These milestones and release candidates have already been declared. Bug owners should retarget these bugs.


1.11 Process to Submit Bugs for PMC Approval - Jeffrey Liu

The new process to sumbit a bug for PMC approval is to add the word PMC to the bug's status whiteboard.

1.12 Versioning of Plug-ins Reused in Other Projects - Jeffrey Liu

TPTP is re-using our Xerces featues and plugins, just like we are re-using the org.eclipse.equinox.servlet.api plug-in from the Equinox component. When WTP and TPTP each builds these features and plugins, they have different 4th digit qualifiers. When an adopter pulls in both WTP and TPTP, there are two copies of the same content floating around. Although there's no known functional problems reported, adopters have expressed concern about this. One suggestion proposed is to hard-code the 4th digit. Any other suggestions/concerns/comments?

2 WTP 1.0.3 Status
- David Williams

2.2 WTP 1.0.3 approved bugs [1] - Jeffrey Liu


3. Other Business - Open

Test coverage for all WTP classes/methods[1]



Jeffrey Liu
IBM Rational Software
IBM Toronto Lab.
8200 Warden Ave. Markham, Ontario, L6G 1C7
Internal mail: D3/UMZ/8200/MKM (D3-268)
T/L: 969 3531
Tel: (905) 413 3531
Fax: (905) 413 4920

Back to the top