Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
2006-12-07
Revision as of 11:05, 6 December 2006 by Jlanuti.us.ibm.com (Talk | contribs)
WTP Development Status Meeting 2006-11-30
- Attendees
- 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].
- 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?
- Bug lists
- Resolved, Unverified (~230)
- Verified, Not closed (~0)
- 1.5.3 Hot Bug Requests (~1)
- 1.5.3 Hot Bugs (~2)
- Blockers, Criticals (~2)
- 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).
- Need to improve the WTP 2.0 Plan document
- Begin to analyze 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.
- Component leads should analyze for two reasons:
- Bug lists
- Untriaged (~115)
- Resolved, Unverified (~70)
- Verified, Not closed (~0)
- 2.0 Hot Bug Requests (~1)
- 2.0 Hot Bugs (~0)
- Blockers, Criticals (~7)
- M4 Shutdown Plans
- 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 for WTP 1.5 <--> WTP 2.0
- 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
- 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
- Investigating running and publishing the automated test coverage reports
- Investigating running Performance and API tests