| [wtp-dev] Agenda of the WTP Status Telecon, 2006-05-11 |
| 136717 | nor | P3 | PC | katep@xxxxxxxxxx | NEW | [action] WS: Review and identify changes in WTP 1.5 that ... | |
| 136716 | nor | P3 | PC | csalter@xxxxxxxxxx | CLOS | FIXE | [action] XML: Review and identify changes in WTP 1.5 that... |
| 136720 | nor | P3 | PC | dpchou@xxxxxxxxxx | CLOS | FIXE | [action] RDB: Review and identify changes in WTP 1.5 that... |
The following action items
are currently open [2]. Action
items owners should update their status in Bugzilla prior to the status
telecon. Thx.
| 136717 | nor | P3 | PC | katep@xxxxxxxxxx | NEW | [action] WS: Review and identify changes in WTP 1.5 that ... |
[2] https://bugs.eclipse.org/bugs/buglist.cgi?short_desc_type=casesubstring&short_desc=%5Baction%5D&product=Web+Tools&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED
2. Help the community
select the right component for bugs - Arthur Ryman
- We'll update the components page [1]
with better descriptions and the names of QA contacts. Each component should
suggest an improved description and a QA contact.
- When reporters don't pick the right component, committers should add
a boilerplate message describing how to pick the right one. The text will
be added to the Committer FAQ [2]
"Thank you for reporting this bug. It has been assigned to the appropriate
component.
For guidance on how to select the appropriate component in future bug reports,
please see
https://bugs.eclipse.org/bugs/describecomponents.cgi?product=Web%20Tools"
[1] https://bugs.eclipse.org/bugs/describecomponents.cgi?product=Web%20Tools
[2] http://www.eclipse.org/webtools/faq/CommitterFAQ.html
3. WTP 1.5 to WTP 2.0
Interoperability - Arthur Ryman
- The requirements be clarified by the PMC [3]
- discuss how to support these requirements. In particular:
“A WTP 1.5 should also be able
to work on projects created by WTP 2.0 users and shared via a repository.
Any new artifacts creates by WTP 2.0 should not break WTP 1.5. WTP 1.5
should either ignore or tolerate any new artifacts created by WTP 2.0.”
- do we have any "brittle"
code in WTP 1.5
[3] http://wiki.eclipse.org/index.php/Web_Tools_Requirements_2.0#Compatibility_with_Other_WTP_Releases
4. WTP 1.0.3 Status
- David Williams
The first time something is released
to a plugin for 1.0.3, its version's service number should be bumped up
by one. Plus, we do not yet, have a good "automatic" solution
for incrementing effected feature version qualifiers, and in the worst
case, will have to do so "manually", by tagging/releasing the
cvs version of effected features ... both so the features service number
is changed the first time, one of its contained plugins change, and from
then on, change it qualifier (cvs version tag) when ever on of its contained
plugins change).
So, if you are the first to release a fix to a plugin, you should up the
version's service number, AND, I suggest, make a note in the bug that you
have done so, (and what version was, and what you changed it to) so there
will be trace of it, in case that makes it easier to manage this.
The end-goal of all this care in versioning is so that, in principle, someone
could "pick up" any build and update a current install with it,
and all the right versions would be installed, and right ones picked at
run time.
4.1 WTP 1.0.3 approved bugs [1] - Jeffrey Liu
[1] http://www.eclipse.org/webtools/plans/1.0.3/ramp-down-bugs-approval.html
5. WTP 1.5 Status
5.1 WTP 1.5 Build Status - David Williams
5.2 WTP 1.5 Hot Bugs
[1] - Jeffrey Liu
[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%20M4&target_milestone=1.5%20M5&target_milestone=1.5%20M6&target_milestone=1.5%20RC1&target_milestone=1.5%20RC2&target_milestone=1.5%20RC3&target_milestone=1.5%20RC4&target_milestone=1.5%20RC5&target_milestone=1.5%20RC6&target_milestone=1.5.1%20M151&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED
5.3 WTP 1.5 Hot Bug
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
5.4 P1 Bugs [1] - Jeffrey
Liu
https://bugs.eclipse.org/bugs/buglist.cgi?classification=WebTools&product=Web+Tools&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&priority=P1
5.5 Blocking Bugs [1]
- Jeffrey Liu
https://bugs.eclipse.org/bugs/buglist.cgi?classification=WebTools&product=Web+Tools&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=blocker
5.6 Bugs to be Triaged
[1] - Jeffrey Liu
https://bugs.eclipse.org/bugs/buglist.cgi?classification=WebTools&product=Web+Tools&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=inbox
6. Other Business -
Open
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