Difference between revisions of "2006-11-16"
(→WTP Development Status Meeting 2006-11-16) |
|||
| Line 56: | Line 56: | ||
:*Website migration to Phoenix and the proposed plan by Arthur. Comments? Do we need a more concrete plan? | :*Website migration to Phoenix and the proposed plan by Arthur. Comments? Do we need a more concrete plan? | ||
:*Does Eclipse have Microsoft Vista plans? Do we? | :*Does Eclipse have Microsoft Vista plans? Do we? | ||
| + | |||
== Teams Status and Focus for Coming Week == | == Teams Status and Focus for Coming Week == | ||
| Line 69: | Line 70: | ||
:;Web Services Component Team | :;Web Services Component Team | ||
| − | :;Dali/JPA | + | :;Java EE Component Team |
| + | |||
| + | :;Dali/JPA | ||
:;JSF | :;JSF | ||
| − | :; | + | :;ATF |
:;Website | :;Website | ||
Revision as of 12:49, 15 November 2006
WTP Development Status Meeting 2006-11-16
- Attendees
- Announcements and Reminders
- Conferences:
- EclipseCon2007 open for long talks, short talks, etc. submissions.
- ECOOP is open for submissions, http://2007.ecoop.org, in Berlin, Germany, July 30 - August 3, 2007.
- Reminder: Make sure your repository connections are using "cvsroot" and not "home"
- Reminder: Next Thursday is a US Holiday - Thanksgiving. No meeting? Go Cowboys!
- WTP 1.5.3
- Due: 2007-02-16
- 1.5.3 Guidelines for fixes -- WTP_Release_1.5.x_Maintenance_Plan_and_Policies
- We will start declaring 1.5.3M builds this week so please smoke test the latest M-build to be declared by noon on Friday.
- There are EMF 2.2.2 builds now, we should step up this week. Thoughts?
- Bug lists
- Resolved, Unverified (~1000)
- Verified, Not closed (~500)
- WTP 2.0
- M3 Due this Friday, 11/17/06
- Please smoke test the latest I-build to be declared as M3 by noon on Friday.
- We are building on Eclipse 3.3 M3, so move up to EMF 2.3 this week?
- What's the Dali status? Still 114 compile errors?
- need to improve Web_Tools_Platform_2.0_Plan document
- List (at least) highest priority items, per component team, by 11/17
- Begin to analyze Adopter Usage Reports to pick most important API requirements
- Bug lists
- Untriaged (~120)
- Blockers, Criticals (~5)
- Note from Lawrence about setting goals for automated testing. Thoughts?
- http://download.eclipse.org/webtools/downloads/drops/R2.0/S-2.0M1-200609010131/apiresults/full_test_coverage/api-tc-summary.html
- Currently 48 plugins without any automated test coverage and 30 with less than 50% coverage.
- Set a specific goal of every plug-in having at least 50% coverage.
- A statement would be required of why 50% coverage is not obtainable (i.e. UI plugins).
- Status reports would be made in the weekly calls.
- Other business?
- Website migration to Phoenix and the proposed plan by Arthur. Comments? Do we need a more concrete plan?
- Does Eclipse have Microsoft Vista plans? Do we?
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
- ATF
- Website
- releng
- Need to figure out how to build-a-feature-patch
- Improved JUnit Console Log results
- Execution Environments
- Add versions 1.5.1,1.5.2,1.5.3 to the WTP bugzilla version options list when opening new bugs
- Compiling non API usage numbers from adopters to establish priorities for declaring new API
- WTP Meeting Archives
- WTP_Development_Status_Meetings