::Build Status? David - There are still failing JUnits. As a reminder to new teams, we should not declare an I build with JUnit failures. JSF to investigate and respin. JPA cannot reproduce on windows, suggest trying on linux.

+

:::In general, if need be and it is appropriate, like a problem with the test itself, you can open a defect against a problematic JUnit, and pull the JUnit from the build.

+

:::We have roughly 200 compiler warnings, which is good progress, but please make this a point of emphasis for next week. David is going to investigate the discouraged access warnings.

+

:::WTP 2.0 now requires a Java5 runtime. However, all components should not assume readiness to start adding hard Java5 dependencies.

+

:::What's the third party jar status? We are going to use Orbit, initial steps done, but to not disrupt builds, David to investigate this later.

+

:::Build process changes - if you are running local builds, there are new environment variables, David to document.

+

:::Please smoke test the latest Integration I-build to be declared by noon on Friday.

+

::FYI, The 2.0 builds will have a combined zip which includes JPA and JSF, possibly ATF, once these projects are promoted past incubation (1Q2007).

::Begin to analyze [http://www.eclipse.org/webtools/development/apiscanner/reports/main.html Adopter Usage Reports] to pick the most important API requirements. Let John know about any suggestions or improvements or open a bugzilla defect against the releng component.

+

:::Component leads should analyze for two reasons:

+

::::*To ensure no one is using code they should not be using.

+

::::*To prioritize which code you plan to make API.

+

::John to send out information about how to run an extension point usage scan.

::The goal of the integration or declared build is to produce a sanity checked target which can be used for development.

+

:::All code should be released by Wednesday night, leaving Thursday to smoke test and declare the build.

+

:::During that period no code should be released unless it is to help declare the build, in which case releasing a map file will trigger a new build and the component lead should send a heads up note discussing the bugzilla, its impact, and why a build was kicked off.

:::The agenda for the upcoming week's meeting will be posted by noon, EST, Wednesday.

+

+

:*Testing Strategies for WTP 2.0

+

::*Smoke Tests

+

:::Each team will have an externally published smoke test scenario.

+

:::A wiki page will be used instead of the mailing list to provide smoke test results.

+

::*Compatibility Tests

+

:::WTP 1.5 -> WTP 2.0

+

::::Each team should create a test scenario to load projects or artifacts from WTP 1.5 and attempt to load, display, edit, and run them on a WTP 2.0 workspace.

+

:::::John will be asking for your test scenario, link, or test plans so start planning this now.

+

::::Possible coordinated compatibility JUnit which will run as part of the builds where each team can add 1.5 metadata or projects and methods to exercise their function on WTP 2.0. Java EE team has a current JUnit to be used as an example.

+

::::Workspace migration testing will mainly consist of a few workspaces with multiple types of content, settings, and a lot of views and perspectives open.

+

::::Questions remain about what exactly we need to test and we will have to gather feedback from each component team. Be wary of anything written out to settings or extension point changes.

+

:::WTP 2.0 -> WTP 1.5

+

::::We should support shared projects in a team environment where one user is on WTP 1.5 and one is on WTP 2.0, so we will need some backwards compatibility testing.

+

::*Milestone Test Passes

+

:::Each Milestone should have a real end game process where we take a step back and ensure quality.

+

:::More formalized test phase with planned activities and platforms:

+

::::Compatibility tests will be run as part of milestone shutdown

+

::::Defect verifications from the current milestone and their closure

+

::::Linux, Windows, Mac

+

::::Investigating better ways to collaborate and encourage the collection of test results

+

+

:*Planning

+

::Current M4 date is January 4th. We will bump this up to late December and update the mailing list.

+

+

+

;Other business?

+

+

:*Java EE 5 Update - Chuck - Initial meeting with good attendance, by end of next week should have a real plan in place.

+

:*EclipseCon Update - Tim W - WTP will have a strong showing, we had more than our allotment of tutorials, and will fill our long talk spots. Other ideas to consider are general WTP 2.0 talks, Dali, Java EE 5, etc. Thanks to all for the large number of quality submissions.

::*The [[Axis2_Integration_in_WTP|Axis2 integration effort]] is in progress. See [https://bugs.eclipse.org/bugs/show_bug.cgi?id=165664 RFE 165664]. Bi-weekly [[Meetings_on_Axis2_Integration_in_WTP|meetings]] are held to discuss progress thru use cases, design and development.

+

+

:;Java EE Component Team

+

+

::*Fixing triaging 1.5.3 defects

+

::*Continuing to triage existing bug lists

+

::*Discussing options for continuing EE5 line items - started calls on Thurs mornings

+

+

:;Dali/JPA

+

+

:;JSF

+

+

::*Refactoring of plugins in progress

+

::*Visual Page designer will be included in the next build

+

::*Investigating Design-time JSP Translation Engine

+

+

:;DTP

+

+

:;ATF

+

+

:;Website

+

+

:;releng

+

+

::*Execution Environments

+

::*Add versions 1.5.1,1.5.2,1.5.3 to the WTP bugzilla version options list when opening new bugs

Build Status? David - There are still failing JUnits. As a reminder to new teams, we should not declare an I build with JUnit failures. JSF to investigate and respin. JPA cannot reproduce on windows, suggest trying on linux.

In general, if need be and it is appropriate, like a problem with the test itself, you can open a defect against a problematic JUnit, and pull the JUnit from the build.

We have roughly 200 compiler warnings, which is good progress, but please make this a point of emphasis for next week. David is going to investigate the discouraged access warnings.

WTP 2.0 now requires a Java5 runtime. However, all components should not assume readiness to start adding hard Java5 dependencies.

What's the third party jar status? We are going to use Orbit, initial steps done, but to not disrupt builds, David to investigate this later.

Build process changes - if you are running local builds, there are new environment variables, David to document.

Please smoke test the latest Integration I-build to be declared by noon on Friday.

FYI, The 2.0 builds will have a combined zip which includes JPA and JSF, possibly ATF, once these projects are promoted past incubation (1Q2007).

The goal of the integration or declared build is to produce a sanity checked target which can be used for development.

All code should be released by Wednesday night, leaving Thursday to smoke test and declare the build.

During that period no code should be released unless it is to help declare the build, in which case releasing a map file will trigger a new build and the component lead should send a heads up note discussing the bugzilla, its impact, and why a build was kicked off.

The agenda for the upcoming week's meeting will be posted by noon, EST, Wednesday.

Testing Strategies for WTP 2.0

Smoke Tests

Each team will have an externally published smoke test scenario.

A wiki page will be used instead of the mailing list to provide smoke test results.

Compatibility Tests

WTP 1.5 -> WTP 2.0

Each team should create a test scenario to load projects or artifacts from WTP 1.5 and attempt to load, display, edit, and run them on a WTP 2.0 workspace.

John will be asking for your test scenario, link, or test plans so start planning this now.

Possible coordinated compatibility JUnit which will run as part of the builds where each team can add 1.5 metadata or projects and methods to exercise their function on WTP 2.0. Java EE team has a current JUnit to be used as an example.

Workspace migration testing will mainly consist of a few workspaces with multiple types of content, settings, and a lot of views and perspectives open.

Questions remain about what exactly we need to test and we will have to gather feedback from each component team. Be wary of anything written out to settings or extension point changes.

WTP 2.0 -> WTP 1.5

We should support shared projects in a team environment where one user is on WTP 1.5 and one is on WTP 2.0, so we will need some backwards compatibility testing.

Milestone Test Passes

Each Milestone should have a real end game process where we take a step back and ensure quality.

More formalized test phase with planned activities and platforms:

Compatibility tests will be run as part of milestone shutdown

Defect verifications from the current milestone and their closure

Linux, Windows, Mac

Investigating better ways to collaborate and encourage the collection of test results

Planning

Current M4 date is January 4th. We will bump this up to late December and update the mailing list.

Other business?

Java EE 5 Update - Chuck - Initial meeting with good attendance, by end of next week should have a real plan in place.

EclipseCon Update - Tim W - WTP will have a strong showing, we had more than our allotment of tutorials, and will fill our long talk spots. Other ideas to consider are general WTP 2.0 talks, Dali, Java EE 5, etc. Thanks to all for the large number of quality submissions.