Jump to: navigation, search

Difference between revisions of "2006-12-07"

Line 112: Line 112:
 
::No status meeting on December 28 and no builds declared December 29th.
 
::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.  Thoughts?
 
::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.  Thoughts?
::Please update your test coverage plans [[WTP_Functional_Test_R20_M4 | for WTP 2.0 M4]]
+
::Please update your [[WTP_Functional_Test_R20_M4 | test coverage plans for WTP 2.0 M4]]
  
  

Revision as of 11:49, 6 December 2006

WTP Development Status Meeting 2006-11-30

Attendees


Announcements and Reminders
  • Conferences:
EclipseCon2007 open for short talk (Jan 15) submissions.
ECOOP open for submissions -- Berlin, Germany, July 30 - August 3, 2007.
  • Reminder:
When you reject a hot bug request as a hot bug, change the summary to [hotbug_declined].
  • Announcement:
Please welcome Dave Gorton as a contributor on BEA's WTP team.


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?
  • Smoke Tests
Please publish your smoke test scenarios by adding a link here.
Please report smoke test status by updating the status page.
  • Bug lists
Resolved, Unverified (~240)
Verified, Not closed (~0)
1.5.3 Hot Bug Requests (~1)
1.5.3 Hot Bugs (~2)
Blockers, Criticals (~3)


WTP 2.0
  • Integration Build this Friday, 12/08/06
Build Status - David?
Compiler warning update - David?
Build process changes - if you are running local builds, there are new environment variables, David to document.
Please smoke test the latest Integration I-build to be declared by noon on Friday.
FYI, The 2.0 builds will have a combined zip which includes JPA and JSF, possibly ATF, once these projects are promoted past incubation (1Q2007).
  • Smoke Tests
Please publish your smoke test scenarios by adding a link here.
Please report smoke test status by updating the status page.
  • 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. Frequency of every 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 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 (~115)
Resolved, Unverified (~70)
Verified, Not closed (~0)
2.0 Hot Bug Requests (~1)
2.0 Hot Bugs (~0)
Blockers, Criticals (~7)
  • Plugin Versioning
As a reminder, there is a helpful wiki explaining Eclipse plugin versioning.
Reminder: In Eclipse, version numbers are composed of four (4) segments: 3 integers and a string respectively named major.minor.service.qualifier.
Each segment captures a different intent:
  • the major segment indicates breakage in the API
  • the minor segment indicates "externally visible" changes
  • the service segment indicates bug fixes and the change of development stream (the semantics attached to development stream is new to this proposal, see below)
  • the qualifier segment indicates a particular build
Plugin and feature versions need not match WTP versions and really should only be updated according to the rules in the wiki.
Be sure to send a heads up note to other teams if you plan on changing plugin versions.
As far as prereq ranges, when should we update the minimum side? David?
  • M4 Shutdown Plans
December 2006
Monday Tuesday Wednesday Thursday Friday
4



5



6



7
Status Call
Smoke Tests

8
1.5.3M Build
2.0I Build
Move to Platform M4 cand.
11



12



13



14
Status Call
Smoke Tests

15
1.5.3M Build
2.0I Build
Move to Platform M4/EMF M4 cand.
18
Verifications
2.0 Function Test

19
Finish tests
2.0 Compatibility Tests

20
Fix critical bugs
2.0M4 candidate build

21
Status Call
Smoke Tests

22
1.5.3M 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. Thoughts?
Please update your test coverage plans for WTP 2.0 M4


Other business?
  • Java EE 5 Update - Chuck?
  • 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
Website
releng
  • Execution Environments
  • 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