Revision as of 14:45, 14 December 2006 by Jlanuti.us.ibm.com
WTP Development Status Meeting 2006-12-14
Announcements and Reminders
Team Status and Focus
- Announcements and Reminders
- EclipseCon2007 open for short talk and demo (Jan 15) submissions.
- 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? Releng JUnit failure?
- Smoke Tests
- Bug lists
- WTP 2.0
- Integration Build this Friday, 12/15/06
- Build Status - David?
- Platform M4 adoption? Classloading issues with our use of Xerces, see 167695.
- JPA JUnit failure?
- Java EE test failure?
- JSF build status?
- John Graham reports smoke test on DTP 1.0 with M4 platform and EMF targets looks good.
- Please smoke test the latest Integration I-build to be declared by noon on Friday.
- Compiler warning update - David?
- Smoke Tests
- 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
- M4 Shutdown Plans
December 2006 Monday Tuesday Wednesday Thursday Friday 4
Move to Platform M4 cand.
Move to Platform M4/EMF M4 cand.
2.0 Function Test
2.0 Compatibility Tests
Fix critical bugs
2.0M4 candidate 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. Dali will do some early sniff testing with DTP and EMF M4. Need to ensure DTP's plugin prereq ranges are compatible with EMF 2.3 M4.
- There is a possible compatibility issue with JEM and EMF M4. Chuck to follow up and do some testing. JEM may just need to rebuild on top of EMF.
- Please update your test coverage plans for WTP 2.0 M4
- Other business?
- Java EE 5 Update - Chuck?
- Renaming ideas for the meta navigator content node under Java EE projects to replace "Deployment Descriptor"?
- There is a wiki page established for people to follow along.
- Any discussion on facets page being skipped when preset is chosen on first page of project creation wizard?
- Website Update - Bob F?
- Is there a doc somewhere for developer workflow, like when builds are, and when to release? David was to investigate 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
- UI plugins and have been added to the local build and source added to the SDK
- Final step is to get Core tests passing and integrated into the build, at which point all of Dali will be integrated
- Meeting scheduled for Friday to make final decision on UI direction for 1.0
- Neil will be out the next couple of weeks with a new baby arriving. Karen Moore will be generally available to cover as needed.
- Weekly I-build will include the Visual Page Designer
- Triaging bugs to highlight areas where we need help
- 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