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.
Difference between revisions of "2007-01-11"
Line 107: | Line 107: | ||
:*Remaining Europa Timeline | :*Remaining Europa Timeline | ||
− | + | ::{|border="2" | |
− | + | |+ January 2007 - February 2007 | |
− | + | ! !! Platform !! +1 !! WTP | |
− | + | |- | |
− | + | ! M5 | |
− | + | | Feb 09 | |
− | + | | Feb 16 | |
− | + | | Feb 23 | |
− | + | |- | |
− | + | ! M6 - API Freeze | |
− | + | | Mar 23 | |
+ | | Mar 30 | ||
+ | | Apr 06 | ||
+ | |- | ||
+ | ! M7 - RC0 | ||
+ | | May 04 | ||
+ | | May 11 | ||
+ | | May 18 | ||
+ | |- | ||
+ | ! RCn... | ||
+ | | | ||
+ | | | ||
+ | | | ||
+ | |- | ||
+ | ! RCX | ||
+ | | Jun 15 | ||
+ | | ? | ||
+ | | ? | ||
+ | |- | ||
+ | ! Europa | ||
+ | | Jun 29 | ||
+ | | Jun 29 | ||
+ | | Jun 29 | ||
+ | |} | ||
+ | |||
:*Smoke Test Scenarios | :*Smoke Test Scenarios | ||
Line 149: | Line 173: | ||
;<span id="Other">Other business?</span> | ;<span id="Other">Other business?</span> | ||
− | |||
:*Java EE 5 Update - Chuck? | :*Java EE 5 Update - Chuck? |
Revision as of 11:03, 10 January 2007
WTP Development Status Meeting 2007-01-11
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.
- EclipseWorld2007, 11/6/2007-11/8/2007 in Reston, VA. The deadline for abstracts is 4/17/2007.
- 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.
- Nominations are open for the Eclipse community awards.
- Announcements:
- Welcome to Pieter Humphrey, taking over for Lawrence Mandel!
- The issues with Eclipse CVS and downloads sites seem to be resolved.
- WTP 1.5.3
- Due: 2007-02-16
- 1/11 - Component leads complete triage scrub of targetted defects.
- 1/26 - WTP PMC review and approval will begin for any changes.
- 2/1 - Release candidates available for testing.
- 2/12 - Zips and update site files ready to start the mirror process.
- 2/16 - Join Callisto Winter Maintenance Release availability.
- 1.5.3 Guidelines for fixes
- We will be declaring a 1.5.3M build this week, so please smoke test and report results using the latest 1.5.3 M build.
- Smoke Test Scenarios
- Please publish your smoke test scenarios by adding a link here.
- Bug lists
- Resolved, Unverified (~300)
- Verified, Not closed (~1)
- 1.5.3 Hot Bug Requests (~0)
- 1.5.3 Hot Bugs (~2)
- Blockers, Criticals (~1)
- Remaining 1.5.3 Targeted Defects (~54)
- WTP 2.0
- Build Status - David?
- Any news on Update Manager issues?
- Component Leads - Other remaining to do for M4 is the new and noteworthy section. Tim W to follow up with Pieter on creating a skeleton page with sections for each component to fill in.
- M5 Proposed Plan
January 2007 - February 2007 Monday Tuesday Wednesday Thursday Friday 08
M5 Planning09
M5 Planning10
M5 Planning11
Status Call
Smoke Test12
Declare I Build15
M5 Development16
M5 Development17
M5 Development18
Status Call
Smoke Test19
Declare I Build22
M5 Development23
M5 Development24
M5 Development25
Status Call
Smoke Test26
Declare I Build29
M5 Development30
M5 Development31
M5 Development01
Status Call
Smoke Test02
Declare I Build05
M5 Development06
M5 Development07
M5 Development08
Status Call
Smoke Test09
Declare I Build
Platform M512
M5 Development
Start component lead change approval13
M5 Development14
M5 Development15
Status Call
Smoke Test16
Declare I Build
EMF M5
Write tests and produce FVT driver19
FVT and compatibility tests20
Defect Verifications
Mustfix defects21
Defect Verifications
Mustfix defects22
Defect Verifications
Status Call
Thumbs Up Test23
Declare WTP 2.0 M5
- Remaining Europa Timeline
January 2007 - February 2007 Platform +1 WTP M5 Feb 09 Feb 16 Feb 23 M6 - API Freeze Mar 23 Mar 30 Apr 06 M7 - RC0 May 04 May 11 May 18 RCn... RCX Jun 15 ? ? Europa Jun 29 Jun 29 Jun 29
- 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.
- Only web services has entered this information, so we will start collecting status from each component next week.
- A JUnit test is fine, but please explain what the JUnit does. These tests only need to be run during milestion test passes.
- 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.
- Rob F to follow up for BEA to contribute these reports.
- Stay tuned in M5 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 (~100) This is way too many, we will start collecting status next week.
- Resolved, Unverified (~150)
- Resolved, Remind or Later (~37)
- Verified, Not closed (~1)
- 2.0 Hot Bug Requests (~0)
- 2.0 Hot Bugs (~0)
- Blockers, Criticals (~3)
- Other business?
- Java EE 5 Update - Chuck?
- There is a wiki page established for people to follow along.
- 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
- 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