Jump to: navigation, search

Difference between revisions of "2006-10-26"

(Status Meeting 2006-10-26 -- added Notes from meeting)
m
 
Line 48: Line 48:
 
:
 
:
  
;Teams Status and Focus for Coming Week
+
== Teams Status and Focus for Coming Week ==
  
 
:;Common Component Team
 
:;Common Component Team
Line 58: Line 58:
 
::1.5.2 testing
 
::1.5.2 testing
 
::Will be branching plugins for 2.0 this week
 
::Will be branching plugins for 2.0 this week
 +
 +
:;Datatools (RDB, 1.5.x only)
 +
 +
::
  
 
:;Editors Component Team
 
:;Editors Component Team

Latest revision as of 14:39, 26 October 2006

WTP Development Status Meeting 2006-10-26

Announcements and Reminders
Congratulations to Jason Sholl, our newest Committer
Planning call this morning went well ... Jochen will sent out minutes/notes from that call.
1.5.2 Release
Bugs needing PMC Approval
Bugs to be verified
Bugs to be verified
Things still to do
Document our WTP_Release_1.5.2_Final_Test
Prepare and test update site(s)
Component Team Leads: must document "ready to release 1.5.2" no later than Monday, 30th, 5 PM Eastern.
announce on Tuesday, 31st (be sure to mention large file/projects performance improvements)
Smoke test final release with spaces in install location directory, and workspace location directory
1.5.3 Release
Due: 2007-02-16
1.5.3 Guidelines for fixes
I did a mass untargeting of 1.5.3, if severity was normal+ and priority was 3+. Bugs went from around 100 to around 50. Even 50 seems like too many too me ... so, triage carefully. I used the following comment when I untargeted these, so if you want to review all I changed, you can search for some substring of this comment.
mass update to remove target for all those targeted to 1.5.3 that were "normal" severity and "priority 3" (on the surface those dont' seem serious enough to fix in a maintenance release). If I have made an error pleasae reset target and set priority appropriately.
Main focus (and contraint) should be on blockers, critical, major, of priority 1 or 2. Otherwise, better to focus on WTP 2.0.
If a bug is within above constraint, then it is up to developer, as long as your team or component lead agrees and has reviewed. (No need for extra documentation). This will be in effect until about January 7th, when more levels of review will be required.
WTP 2.0
M3 Due 11/17
Please smoke test latest I-build to be declared by noon on Friday.
RDB has been removed.
Other business?

Teams Status and Focus for Coming Week

Common Component Team
Server Component Team
1.5.2 testing
Will be branching plugins for 2.0 this week
Datatools (RDB, 1.5.x only)
Editors Component Team
1.5.3 Testing and Triage
Web Services Component Team
1.5.2 - Fix to critical bug 161250 released.
1.5.2 - Testing.
1.5.3 - Triaging bugs in/out of the release.
2.0 - Triaging RFEs for inclusion in the plan.
Project Component Team
JEE Component Team
1.5.2 Testing , Triaging 1.5.3/2.0