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.

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.

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

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

Other business?

Java EE 5 Update - Chuck?

EclipseCon Update - Tim W?

Website Update - Tim W?

Just a friendly reminder to fill in your team status each week on the meeting agenda.

Teams Status and Focus for Coming Week

Common Component Team

Server Component Team

Datatools (RDB, 1.5.x only)

XML/JSP Component Team

Web Services Component Team

Java EE Component Team

Dali/JPA

JSF

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