:Update from PMC - Tim D has made a proposal on behalf of IBM for a WTP 1.5.4. The PMC accepts the release and is reviewing the proposed plan. More information should be available next week, however to set expectations, all proposed defect fixes will be PMC reviewed.

::Component Leads should be considering their proposed bugzilla line items for M6.

+

::Action Item for Component Leads to target their proposed bugzilla line items for M6 by end of day, Wednesday Feb 28.

::How should we capture this proposed plan information, knowing it will be dynamic as the milestone progresses?

::How should we capture this proposed plan information, knowing it will be dynamic as the milestone progresses?

−

:::Suggestion 1: Bugzilla enhancements are targetted for the release like "2.0", not a milestone, and in whiteboard, enter, "proposed M6"

+

:::At the beginning of a release, all proposed bugzilla's should initially be targetted to the release, i.e. "2.0"

−

:::Suggestion 2: Bugzilla enhancements are targetted for a specific milestone upfront like "2.0 M6", and in whiteboard, enter "proposed"

+

:::During the planning week for each milestone, bugzilla enhancements for that milestone are targetted accordingly to the current milestone, i.e. "2.0 M6". This is to avoid long term planning and over promising unrealistic commitments.

−

:::ThoughtS? Other suggestions?

+

:::At the first status call for a milestone, we will review the proposed line items from each component.

+

:::At any point in the milestone we can gauge an accurate picture of the happenings and plans for the remainder of that milestone.

+

+

:*Hot Bugs

+

::As we enter M6, "hot bug season" is upon us, so please urge adopter companies to not be complacent about their bugs, but to proactively ensure they are targetted appropriately and to raise as hot bugs when necessary.

::Kathy - IP legal approval is still ongoing so line items have been deferred to M6. However there is axis 2 runtime support and are just ironing out issues for the EclipseCon demo's. Check out the [http://wiki.eclipse.org/index.php/Axis2_Integration_in_WTP Axis2 Integration in WTP wiki] for details.

:*Website

:*Website

−

::Bob F - We are live on the Phoenix look and feel! Please file bugs or enhancements on component 'web site' if you encounter problems.

+

::Bob F - We are live on the Phoenix look and feel! Please file bugs or enhancements on component 'web site' if you encounter problems or if you need anything before EclipseCon especially.

−

+

::Working on communit resources now as well as the new and noteworthy's for M4 and M5.

+

::We can close original bug to migrate website to php.

+

::Helping JPA set up a php expert to migrate their webpages, will help other teams if they want. Raghu will enlist help for JSF.

=== Other business? ===

=== Other business? ===

Line 180:

Line 198:

==== Web Services Component Team ====

==== Web Services Component Team ====

+

:*WTP 1.5.3 - Done.

+

+

:*WTP 1.5.4 - About half a dozen bugs with status whiteboard set to "WTP 1.5.4".

+

+

:*WTP 2.0 - Ongoing triaging of RFEs for inclusion in the plan.

+

:**Apache Axis2 - The [[Axis2_Integration_in_WTP|Axis2 integration effort]] is in progress. See [https://bugs.eclipse.org/bugs/show_bug.cgi?id=165664 RFE 165664]. Weekly [[Meetings_on_Axis2_Integration_in_WTP|meetings]] continue. [[Use cases for Axis2 Integration in WTP|Use cases]] and [[Requirements document for Axis2 Integration in WTP|requirements]] drafted. Secondary RFEs are open and targetted to M6.

+

:***Lahiru Sandakith (WSO2) has developed and attached the first round of new plugins for Axis2 supporting bottom-up and top-down scenario. Legal and technical review commencing (See [https://bugs.eclipse.org/bugs/show_bug.cgi?id=168762 RFE 168762]).

WTP 1.5.3

WTP 1.5.4

Update from PMC - Tim D has made a proposal on behalf of IBM for a WTP 1.5.4. The PMC accepts the release and is reviewing the proposed plan. More information should be available next week, however to set expectations, all proposed defect fixes will be PMC reviewed.

Action Item for Component Leads to target their proposed bugzilla line items for M6 by end of day, Wednesday Feb 28.

How should we capture this proposed plan information, knowing it will be dynamic as the milestone progresses?

At the beginning of a release, all proposed bugzilla's should initially be targetted to the release, i.e. "2.0"

During the planning week for each milestone, bugzilla enhancements for that milestone are targetted accordingly to the current milestone, i.e. "2.0 M6". This is to avoid long term planning and over promising unrealistic commitments.

At the first status call for a milestone, we will review the proposed line items from each component.

At any point in the milestone we can gauge an accurate picture of the happenings and plans for the remainder of that milestone.

Hot Bugs

As we enter M6, "hot bug season" is upon us, so please urge adopter companies to not be complacent about their bugs, but to proactively ensure they are targetted appropriately and to raise as hot bugs when necessary.

Working Groups

Java EE 5

Basic support for JEE 5 underway (facets, delegates)

Waiting on plan from Chuck for publishing the extension API

Axis2

Kathy - IP legal approval is still ongoing so line items have been deferred to M6. However there is axis 2 runtime support and are just ironing out issues for the EclipseCon demo's. Check out the Axis2 Integration in WTP wiki for details.

Website

Bob F - We are live on the Phoenix look and feel! Please file bugs or enhancements on component 'web site' if you encounter problems or if you need anything before EclipseCon especially.

Working on communit resources now as well as the new and noteworthy's for M4 and M5.

We can close original bug to migrate website to php.

Helping JPA set up a php expert to migrate their webpages, will help other teams if they want. Raghu will enlist help for JSF.

WTP BOF - We have an official BOF scheduled for Monday March 5th, 7:30 PM - 8:45 PM, room 209. More details still being worked out, but if interested, please go ahead and add a +1 planning on attending comment to the eclipsezilla so we can have an accurate number of attendees.

EclipseWorld2007, 11/6/2007-11/8/2007 in Reston, VA. The deadline for abstracts is 4/17/2007.

Reminder:

Please come to the meeting with your smoke test results posted to the wiki and ready to vote on declaration of the weekly builds.