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

See WTP Status Telecons [1] for more information.



Amy Wu

Chris Bealey
Chuck Bridgham

Cameron Bateman
Der Ping Chou
Jeffrey Liu
John Lanuti

Kate Price

Kathy Chan
Keith Chong
Lawrence Mandel

May Zhu
Nitin Dahyabhai

Rob Frost
Ted Bashor

1. Action Items - Jeffrey Liu
122187 nor P3 naci.dai@xxxxxxxxxxxxx REOP 1.0.1 M101 [action] Generate reports of fixed bugs from CVS commit c...
148279 nor P3 csalter@xxxxxxxxxx NEW --- [action] Fill in WTP 1.5 XML new and noteworthy details
148280 nor P3 cbrealey@xxxxxxxxxx ASSI --- [action] Fill in WTP 1.5 WS new and noteworthy details
148281 nor P3 dpchou@xxxxxxxxxx NEW --- [action] Fill in WTP 1.5 RDB new and noteworthy details
148282 nor P3 cbridgha@xxxxxxxxxx NEW --- [action] Fill in WTP 1.5 J2EE new and noteworthy details
148681 nor P3 wst.wsi-inbox@xxxxxxxxxxx NEW --- [action] Create a test plan for the wst.wsi component

6 bugs found.

2. WTP 1.5 Status - David Williams

Nitin - Will we rebuild the all-in-one zips using the final builds from our prereqs? We are using the latest RC builds right now.

Jeff - No need if our prereqs simply rename their RC builds and call that final. We'll need to rebuild the all-in-one zips if our prereqs rebuild.

2.1 WTP 1.5.1 Branching Strategy - Jeffrey Liu

Branch name:

Please remember your plug-in version needs to be updated on the first change in the 1.5.1 stream (+100 rule)

Two branching methods were proposed:

1. Branch on first change (require retrofit back to the 2.0 stream)

2. Branch on first known difference between 1.5.1 and 2.0

Bring your comments/suggestions/concerns...

Ted - Maybe confusing to users if plug-ins are not branched on first change. Users need to know what tag to use for the maintenance release.

Jeff - We can create a document that documents the procedure?

Chuck - Please include information on releasing changes to both the maintenance release and HEAD. In the past, our team was caught a few times not releasing to both streams.

Ted - Does CVS has any facility to remind us of un-release changes.

Lawrence - No.

Jeff - [action] Jeff will reate a document and ask for feedbacks.

2.2 New Site Coverage - Lawrence Mandel

2.3 Bugs to be Verified [1] and Closed [2] - Jeffrey Liu  

We are down to 2023 un-verified bugs to 1587 and 508 un-closed bugs to 285. Great progress, thanks everyone. Keep it up.



2.3 Test Coverage [1] - Jeffrey Liu

Jeff - The RDB component has very little test coverage.

Der Ping - We have no JUnit tests, creating more JUnit testcases remains a todo for us.

Jeff - You guys have testcases that you run for smoke tests, etc. Can you add those testcaess to the RDB test plan?

Chuck - Difficult to do UI testing in a JUnit. We can add JUnit testcases for simple stuff such as opening perspectives/views/editors.

Rob - Adopters have a large set of UI driven tests. We can ask them to contribute testcases, or learn from them about how they are doing UI testings. Perhaps even get test results/data from them.

Lawrence - We need to be careful, our test effort needs to be done in the open. Adopters can provide test results on builds, but we should not rely on adopters to carry out the testing for us.

Jeff - We should also ask for a JUnit testcase whenever we receive a patch.

2.4 Performance - Jeffrey Liu

Chuck - Looks like some of our tests are not running.

Jeff - Let's get in touch offline to sort it out.

3 WTP 1.0.3 Status - David Williams

4. Other Business - Open

Congrats Cameron Bateman on being a committer.

Keith - Any reason why we are not using the Wiki for news and noteworthy.

Lawrence - To be consistent with the platform

Lawrence - Request for outstanding contributors in WTP 1.5. For details, refer to bug 148268

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