Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
2006-12-21
Revision as of 11:12, 20 December 2006 by Unnamed Poltroon (Talk)
WTP Development Status Meeting 2006-12-14
Outline
Attendees
Announcements and Reminders
WTP 1.5.3
WTP 2.0
Other business?
Team Status and Focus
- Attendees
- Announcements and Reminders
- Conferences:
- EclipseCon2007 open for short talk and demo (Jan 15) submissions.
- Reminder:
- When you reject a hot bug request as a hot bug, change the summary to [hotbug_declined].
- When requested, be sure to update the smoke test results status page.
- In order to launch and test an Eclipse M4 workbench you must upgrade to an eclipse M4 platform driver for your development environment.
- Announcements:
- Nominations are open for the Eclipse community awards.
- WTP 1.5.3
- Due: 2007-02-16
- 1.5.3 Guidelines for fixes
- We will not be declaring a 1.5.3M build this week so no 1.5.3 smoke tests.
- Smoke Test Scenarios
- Please publish your smoke test scenarios by adding a link here.
- Bug lists
- Resolved, Unverified (~275)
- Verified, Not closed (~0)
- 1.5.3 Hot Bug Requests (~0)
- 1.5.3 Hot Bugs (~2)
- Blockers, Criticals (~4)
- WTP 2.0
- Build Status - David?
- We are building with a patched JEM and cannot officially declare M4 until we have a real build from JEM, which will hopefully be in line for the January 4th Europa date.
- JSF problems with EMF API change – 168484 - Raghu?
- Out of memory issues with Sun JDK - Kathy?
- Only teams dropping critical or blocker defects need to re-smoke the build for Friday.
- Compiler warning update - David?
- Smoke Test Scenarios
- Please publish your smoke test scenarios by adding a link here.
- 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 in 2007 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.
- Need to improve the WTP 2.0 Plan document
- Bug lists
- Untriaged (~84)
- Resolved, Unverified (~130)
- Verified, Not closed (~1)
- 2.0 Hot Bug Requests (~1)
- 2.0 Hot Bugs (~0)
- Blockers, Criticals (~6)
- M4 Shutdown Plans
December 2006 Monday Tuesday Wednesday Thursday Friday 18
Produce M4 candidate
19
Verifications
2.0 Function Test
20
Finish tests
2.0 Compatibility Tests
21
Status Call
Smoke Tests
22
Move to EMF M4
Declare WTP2.0 M401
Holiday
02
03
Update JEM
04
Status Call
Smoke Tests
Declare WTP 2.0 M4
05
- No status meeting on December 28 and no builds declared December 29th.
- Need to ensure DTP's plugin prereq ranges are compatible with EMF 2.3 M4.
- Please update your test coverage plans for WTP 2.0 M4
- Other business?
- Java EE 5 Update - Chuck?
- There is a wiki page established for people to follow along.
- Website Update - David?
- Is there a doc somewhere for developer workflow, like when builds are, and when to release? David investigating broken links and adding an updated doc.
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
- 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