Jump to: navigation, search

Difference between revisions of "2007-01-11"

(<span id="Status">Teams Status and Focus for Coming Week</span>)
(<span id="Status">Teams Status and Focus for Coming Week</span>)
Line 193: Line 193:
  
 
:;XML/JSP Component Team
 
:;XML/JSP Component Team
 +
 
::** resuming work on 1.5.3 hot bug
 
::** resuming work on 1.5.3 hot bug
 
::** Fixing minor bugs as the remainder of the team returns from vacation
 
::** Fixing minor bugs as the remainder of the team returns from vacation

Revision as of 15:06, 11 January 2007

WTP Development Status Meeting 2007-01-11

Outline
Attendees
Announcements and Reminders
WTP 1.5.3
WTP 2.0
Working Groups
Other business?
Team Status and Focus


Attendees


Announcements and Reminders
  • Announcements:
  • Some WTP PMC Transitions
  • 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 until January 22 for the Eclipse community awards.


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/2 - Release candidates available for testing.
2/5-2/9 - Test and Defect Verifications - No more changes after 2/9.
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 (~325)
Verified, Not closed (~20)
1.5.3 Hot Bug Requests (~0)
1.5.3 Hot Bugs (~2)
Blockers, Criticals (~1)
Remaining 1.5.3 Targeted Defects (~49)


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. Pieter?
  • M5 Proposed Plan
January 2007 - February 2007
Monday Tuesday Wednesday Thursday Friday
08
M5 Planning
09
M5 Planning
10
M5 Planning
11
Status Call
Smoke Test
12
Declare I Build
15
M5 Development
16
M5 Development
17
M5 Development
18
Status Call
Smoke Test
19
Declare I Build
22
M5 Development
23
M5 Development
24
M5 Development
25
Status Call
Smoke Test
26
Declare I Build
29
M5 Development
30
M5 Development
31
M5 Development
01
Status Call
Smoke Test
02
Declare I Build
05
M5 Development
06
M5 Development
07
M5 Development
08
Status Call
Smoke Test
09
Declare I Build
Platform M5
12
M5 Development
Start component lead change approval
13
M5 Development
14
M5 Development
15
Status Call
Smoke Test
16
Declare I Build
EMF M5
Write tests and produce FVT driver
19
FVT and Compatibility Tests
20
Defect Verifications
Mustfix defects
21
Defect Verifications
Mustfix defects
22
Defect Verifications
Status Call
Thumbs Up Test
23
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
  • To ensure no one is using code they should not be using.
  • To prioritize which code you plan to make API.
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 (~50) Good progress, but still too many.
Resolved, Unverified (~160)
Resolved, Remind or Later (~37)
Verified, Not closed (~23)
2.0 Hot Bug Requests (~0)
2.0 Hot Bugs (~0)
Blockers, Criticals (~1)


Working Groups
  • Java EE 5 Update - Chuck/Naci?
There is a wiki page established for people to follow along.
  • Axis2 - Kathy/Chris?
  • Website Update - Bob F?
Other business?

Teams Status and Focus for Coming Week

Common Component Team
Server Component Team
Datatools (RDB, 1.5.x only)
XML/JSP Component Team
    • resuming work on 1.5.3 hot bug
    • Fixing minor bugs as the remainder of the team returns from vacation
Web Services Component Team
Java EE Component Team
  • Evaluate and refine initial design and code for functionality that supports attribute-based mapping of Java classpath entries into the virtual component tree.
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


Back to WTP Meeting Archives
Back to Web Tools Wiki Home