Skip to main content
Jump to: navigation, search

Difference between revisions of "2006-12-07"

(JSF status)
Line 141: Line 141:
::*First cut of the [[Release_1.0_Milestones|Release 1.0 Milestone plan]] released

Revision as of 14:27, 7 December 2006

WTP Development Status Meeting 2006-12-07


Announcements and Reminders
  • Conferences:
EclipseCon2007 open for short talk (Jan 15) submissions.
ECOOP open for submissions -- Berlin, Germany, July 30 - August 3, 2007.
  • Reminder:
When you reject a hot bug request as a hot bug, change the summary to [hotbug_declined].
  • Announcements:
Please welcome Dave Gorton as a contributor on BEA's WTP team.
Please welcome Carl Anderson as a contributor on IBM's WTP team.
Web Services working group formed for integrating Apache Axis2 into WTP. Refer to the wiki page. Kathy?

WTP 1.5.3
  • Due: 2007-02-16
  • 1.5.3 Guidelines for fixes
  • We will be declaring a 1.5.3M build this week so please smoke test the latest M-build to be declared by noon on Friday.
Build status - David?
  • Smoke Tests
Please publish your smoke test scenarios by adding a link here.
Please report smoke test status by updating the status page.
  • Bug lists
Resolved, Unverified (~240)
Verified, Not closed (~0)
1.5.3 Hot Bug Requests (~1)
1.5.3 Hot Bugs (~2)
Blockers, Criticals (~3)

WTP 2.0
  • Integration Build this Friday, 12/08/06
Build Status - David?
Compiler warning update - David?
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).
  • Smoke Tests
Please publish your smoke test scenarios by adding a link here.
Please report smoke test status by updating the status page.
  • Compatibility Tests for WTP 1.5 <--> WTP 2.0
Information on what to test and how to publish your compatibility test plans can be found here.
  • Performance and API Tests
Need to investigate re-enabling these tests for M5. We will publish these results with every weekly declared build.
  • Usage Reports
The Adopter Usage Reports are posted for component owners...
  • To ensure no one is using code they should not be using.
  • To prioritize which code you plan to make API.
The Extension Point Usage Reports are also posted. The instructions for adopters on how to contribute can be found here.
Stay tuned for automated test coverage report numbers based on using TPTP's line coverage analysis tools. Also investigating cross referencing the data from the usage reports to detail where test coverage must be improved.
  • Bug lists
Untriaged (~115)
Resolved, Unverified (~90)
Verified, Not closed (~1)
2.0 Hot Bug Requests (~0)
2.0 Hot Bugs (~0)
Blockers, Criticals (~7)
  • Plugin Versioning
As a reminder, there is a helpful wiki explaining Eclipse plugin versioning.
In Eclipse, version numbers are composed of four (4) segments: 3 integers and a string respectively named major.minor.service.qualifier.
Each segment captures a different intent:
  • the major segment indicates breakage in the API
  • the minor segment indicates "externally visible" changes
  • the service segment indicates bug fixes and the change of development stream (the semantics attached to development stream is new to this proposal, see below)
  • the qualifier segment indicates a particular build
Plugin and feature versions need not match WTP versions and really should only be updated according to the rules in the wiki.
Be sure to send a heads up note to other teams if you plan on changing plugin versions.
As far as prereq ranges, the lower bound for WTP to WTP should be bumped up accordingly, and for WTP prerqs outside of WTP, the lower bound should only be updated if there are reasons which preclude the scenario from working.
  • M4 Shutdown Plans
December 2006
Monday Tuesday Wednesday Thursday Friday



Status Call
Smoke Tests

1.5.3M Build
2.0I Build
Move to Platform M4 cand.



Status Call
Smoke Tests

1.5.3M Build
2.0I Build
Move to Platform M4/EMF M4 cand.
2.0 Function Test

Finish tests
2.0 Compatibility Tests

Fix critical bugs
2.0M4 candidate build

Status Call
Smoke Tests

1.5.3M Build
Move to EMF M4
Declare WTP2.0 M4

No status meeting on December 28 and no builds declared December 29th.
Dali 1.0 is December 22. They are okay with EMF plans, but they have a DTP dependency. DTP 1.0 prereqs EMF 2.2.1. Thoughts? Dali, can you guys do some early sniff testing with DTP and EMF M4?
There is a possible compatibility issue with JEM and EMF M4. Update?
Please update your test coverage plans for WTP 2.0 M4

Other business?
  • Java EE 5 Update - Chuck?
  • Website Update - Bob F?

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
  • Having problems with ATF's dependency on Mozilla's XULRunner browser. Mozilla won't commit to doing the builds ATFs for Windows and Mac. The Mac build also requires them to integrate our fixes that are required to integrate the Mozilla's browser in eclipse on Mac. This will push out the Tech Preview planned for January. A lot of Ajax programmers use Macs, so it doesn't make sense to do a preview without this support.
  • Starting to drop the changes to simplify install by better handling of Ajax runtime handling.
  • Starting to make changes to build process to automate the builds and fit as closely as possible to the WTP Build Process and Procedures. Since ATF has a fragment for the SWT Browser plugin, ATF has to deal with platform specific issues. The fragment needs to be built for each platforms using the jars and classpath for the SWT Browser plugin specific for that platform.
  • Add versions 1.5.1,1.5.2,1.5.3 to the WTP bugzilla version options list when opening new bugs
  • Investigating running and publishing the automated test coverage reports
  • Investigating running Performance and API tests

Back to WTP Meeting Archives

Back to the top