| [wtp-dev] Minutes of the WTP Status Telecon, 2006-08-24 |
9/01: Component lead triage begins. All bugs reviewed and targeted accordingly; most P3 and low sev bugs not yet addressed that are nontrivial should be pushed out of the 1.5.1 release.
9/08: WTP 1.5.1 code complete. Start of PMC-level triage.
9/15: Code freeze for WTP 1.5.1 and start of downstream projects’ (TPTP, e.g.) final readiness and verification cycle. (Any requested changes or P1 bugs discovered required PMC approval to fix.)
9/15: Date by which all Callisto projects are maintenance build ready and update site loading/testing can commence.
9/27: Final posting of Callisto bits and mirror synchronization; update site locked during this time.
9/29: GA for first Callisto maintenance pack (including base 3.2.1 and WTP 1.5.1). Callisto update site, WTP update site, and WTP download page all available.(including all-in-one bundles for WTP 1.5.1).
David - Respin in progress. Some failing JUnit. This is the one we should smoke test on.
David - We have started a document for workflow conventions and meaning of different bugzilla fields. I welcome everyone to have a look and improve it.
http://wiki.eclipse.org/index.php/WTP_Bugs%2C_Workflow_and_Conventions
David - Consider fixing
the fix-able internal API usages in 1.5.1 Jeff - We have quite a few 1.5.1 targeted bugs in the J2EE
component and the XML Web service component. Are those accurate?
John - Yes, maybe a couple will fall out, NL, TVT, etc.
But they are accurate.
Keith - Yes, they are accurate.
David - We have little time left before shutdown. We should
be careful what to fix (serious bugs, etc).
1.2 Bugs sitting at
inboxes [1] - Jeffrey Liu Jeff - We have quite a few in the XML Web service and RDB
component, can we get them triaged by next week?
Der Ping - Yes.
Keith - The XSD component is done. Richard to triage the
ones in the WSDL component.
1.3 Hot Bugs [1] - Jeffrey
Liu 2. WTP 2.0 Status -
David Williams
David - We do have builds working now
and all JUnits passing.
David - We said we will have our 1st
milestone on the 24th, but we don't have any declared builds yet. So let's
smoke test our 2.0 build this week and declare a build tomorrow. Assuming
no serious problem, we can declare our M1 build next week.
Raghu - There are some DNF JSF tests,
what does it mean? They were running in 1.5.1.
David - Did Not Finish.
David - There's a related bug on PPC
and linux, for more info, refer to https://bugs.eclipse.org/bugs/show_bug.cgi?id=154856
Jeff - Could be a typo in the ant script
(test.xml).
1.1 Bugs targeted to 1.5.1 [1] - Jeffrey Liu
We still have 67 bugs targeted to 1.5.1. According to plan, we need to
review and target these bugs correct by next week. Most P3 and low sev
bugs will be deferred.
[1] https://bugs.eclipse.org/bugs/report.cgi?x_axis_field=bug_severity&y_axis_field=component&z_axis_field=&query_format=report-table&classification=WebTools&product=Web+Tools&target_milestone=1.5.1+M151&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&format=table&action="">
We have 83 bugs sitting at inboxes. Did we triage them? If not, I am worry
that we may have missed something important.
[1] https://bugs.eclipse.org/bugs/report.cgi?x_axis_field=bug_severity&y_axis_field=assigned_to&z_axis_field=&query_format=report-table&classification=WebTools&product=Web+Tools&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=regexp&email1=.*inbox.*&format=table&action="">
[1] https://bugs.eclipse.org/bugs/buglist.cgi?short_desc_type=allwordssubstr&short_desc=%5Bhotbug%5D&classification=WebTools&product=Web%20Tools&target_milestone=1.5.1%20M151&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED
1.4 Hot Bugs Requests [1] - Jeffrey Liu
[1] https://bugs.eclipse.org/bugs/buglist.cgi?short_desc_type=allwordssubstr&short_desc=%5Bhotbug_request%5D&classification=WebTools&product=Web%20Tools&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED
3. Other Business - Open
Konstantin - Wanted to review the use
of release targets (in addition to milestone targets)
Konstantin - In the past, we've been
rolling targets from milestone to milestone, which doesn't seem right.
If we are committed to fix a bug in a release, but have no idea when it
will be fixed, then we should use the release target.
David - Good idea to me, what's the
difference between untargeted vs. release targeted
Ted - You wouldn't want to target everything
to the next release because once a bug is targeted, we are committed to
fix it in that release.
David - Sounds good, just be careful
that what we don't over-promise what we are going to fix.
[action]
David to create bugzilla targets for 1.5.2 and 2.0
Lawrence - Accepted another opportunity.
Will reduce partipation in WTP. Tim will take over the role of ecosystem
lead.
David/Tim - Thank you Lawrence for all
the great work that he has done.
Thanks,
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
jeffliu@xxxxxxxxxx