WTP 2008-02-21

WTP Development Status Meeting 2008-02-21

Attendees

Project Leads
Konstantin	Y
Tim	N
Nitin	Y
Kathy	Y
Chuck	N
Naci	N
Raghu	Y
Neil	Y
David	Y
Helen	Y

Committers
Bob	Y
Carl	Y
Dave	N
Phil	Y
Kaloyan	Y
Larry	Y
Amy	Y
Kate	N
Angel	Y
Rob	Y
Brad	N

Friends
Nick	Y

Announcements And Reports

WTP 2.0.2 to be declared Monday Feb 25, RC3 to be declared this week
WTP 3.0 M5 declared on Monday 2/18, Congrats & Thank you! : )
M5 New and Noteworthy

Minutes:

Nitin: Ensure all contents are on time, send a note on mailing list?

Helen: will also add to annoucements the week before

Focus on Backlog and Quality metrics (Neil)

Neil: Current focus item updated

Current Focus Item:

Untargeted bugs with patches attached opened before January 1st, 2008 (Last week - 74; Currently ~ 70)

Options are

Target bug for a release or "future"
Mark as Invalid or Wont Fix

Upcoming Focus Item:

Past Focus Items:

Untargeted Enhancements opened before January 1st, 2007 (Last week - 82; Currently ~ 62)

Before July 1st, 2007 - 116
Options are

Invalid - Enhancement does not fit with the scope of the project or is already implemented.
helpwanted keyword - This is a valid request, but due to committer resources and other priorities, outside help will be needed to make this happen.
Future - I would use this in conjunction with the helpwanted keyword. I use this for legitimate requests that are important but will not make any planned release, but likely will make a future release.

Untargeted severity "Major" and higher bugs opened before January 1st, 2007 (Last week - 2; Currently ~ 0)

Before July 1st, 2007 - 21

Where did they all go?

Minutes

Neil: wst.xml is leading in current focus item

Nitin: will look into them for next week

Focus on Requirements Planning (Raghu)

Review and Update the WTP 3.0 Plan by ....

Projects with no committed items: none

Please update status page

Please review untriaged enhancement requests

Untriaged Enhancement Requests ()

Plan items in Bugzilla ()

Minutes

Raghu: keep it open till end of M6 for fine tuning (April 7)

WTP 2.0.2

Schedule - Details...

Last M Build Jan 18
Feb 1 RC1
Feb 15 RC2 (RC2, bugs from Feb 1 - Feb 15 will need 1 PMC approval vote)
Feb 22 RC3 (RC3 only if necessary, bugs from Feb 15 -> Feb 22 will need 2 PMC approval votes)
Feb 25 2.0.2 WTP GM
Feb 29 2.0.2 Public access

Build

RC3 build M-2.0.2RC3-20080221101112/

2.0.2 RC3 Smoketest

202 Shutdown Test Plan

202 Shutdown

Bug Lists

All Remaining 2.0.2 Targeted Bugs (~17)

2.0.2 Hot Bug Requests (~0)

2.0.2 Hot Bugs (~0)

2.0.2 Bugs for PMC Approval (~0)

2.0.2 Untargeted Blockers/Criticals (~0)

2.0.2 Blockers/Criticals (~0)

2.0.2 Total JST, WST, JSF Bugs Fixed (~95)

2.0.2 Dali Total Bugs Fixed (~10)

2.0.2 Resolved, Unverified Blockers/Criticals (~23) By Assignee

Minutes:

Helen: Shutdown test plan to be completed before we declare on Feb 25

Remaining 2.0.2 Targeted Bugs to be closed if already fixed or moved out of 202

Kathy: need a new and noteworthy for 202?

Nitin:releasenotes only for 202, will send a note out by eod today

David: usually a bug that lists the total # of bugs

WTP 3.0 M6

our +2 date: Monday, April 7 2008
Final Code released by March 28th

Plan 02/18 - 02/22

Development 02/25 - 03/28

Test 03/31 - 04/04

Bug Lists

3.0 Invalid Targeted Bugs (~3)

3.0 M6 Targeted Bugzilla Enhancements (~19)

All Remaining 3.0 Targeted Enhancements (~164)

3.0 M6 Remaining Targeted Bugs (~121)

3.0 M6 Hot Bug Requests (~0)

3.0 M6 Hot Bugs (~0)

3.0 M6 Blockers/Criticals (~0)

3.0 M6 JST, WST, JSF Bugs Fixed (~17)

3.0 M6 JPT Dali Bugs Fixed (~24)

3.0 Untargeted Blockers/Criticals (~0)

3.0 Resolved, Unverified Blockers/Criticals (~33) By Assignee

Minutes:

Dev week next week, I build to be declared next week

Other business?

WTP API Policy - Tim D

David: Any objections to be voiced by next Thursday's meeting, any questions pls post to mailing list

Tim will cover again next week

build break board

Helen will start for next week M6 build, will send it out to mailinglist once wiki is ready

Helen will post failure on wiki and dev leads to post reasons/cause of issues.

David: change how we generate our javadoc in the build, checking with who wants to help out with this

can check with Nick Bolt on this, Tim has volunteered in the server componnet for M6

David: Jee package, anyone gave it a try?

Kathy: ran webservices smoketest, and looks like

Amy: looks good for XML as well

Teams Status and Focus for Coming Week

Source Editing

Ongoing triaging of incoming bug reports
Working on updating bug backlogs
Planning for M6

Server Tools

Web Services/WSDL

Ongoing triage of incoming and existing bugs/RFEs.
Fixing bugs and implementing RFEs.
Planning for M6.

Java EE

Dali JPT

JPT 2.0
- Dali Java Context Model status
- Dali Orm.xml Context Model status
- Rolled back to previously released code. Will release the new code for the first M6 I-Build.

JSF

Planning for M3
Property Editor prototype
JSPX support investigation
XHTML support investigation

releng

will soon remove wst common ui properties. See bug 131862.

will soon start signing all jars. Teams will have to be on the look out for performance problems, in M6. If any, it would effect those cases where custom class loaders are used, as that might result in repeated class

verification.

References

Eclipse 3.4 Project Plan for the Ganymede Simultaneous Release. WTP Performance Tests Tweaking the Access Rules for WTP

Branching Strategy

Please review and comment on the WTP How to: Branching Policy and Practices guide.

In general, the minimum is if you branch a plug-in to branch all the plug-ins in the corresponding map file. It is fine to branch everything if you choose as well. We may need to reorganize map files slightly and we can investigate that on a case by case basis. This is intended to be a living document and open to evolutions and improvements.

Instructions for tagging existing and new WTP wiki pages can be found at WTP's Category page; remember, we can create subcategories as well
This Week's Smoke Test Results

WTP Smoke Test Results R30