Jump to: navigation, search

Difference between revisions of "DTP PMC and Project Lead Meeting Minutes: July 21, 2008"

(Agenda)
(Agenda)
Line 15: Line 15:
  
 
==Agenda==
 
==Agenda==
*Revised dates for 1.6.1 M1/M2/release (More info forthcoming...)
 
 
*Updated plan for 1.6.1 M1 release
 
*Updated plan for 1.6.1 M1 release
**We will use the 7/25 build as the 1.6.1 M1 milestone build.  
+
**We will use the '''July 25''' build as the 1.6.1 M1 milestone build.  
 
**Though there will be a 2 week rampdown and testing period for M1, committers can continue to develop into the HEAD branch for the daily M2 build.  
 
**Though there will be a 2 week rampdown and testing period for M1, committers can continue to develop into the HEAD branch for the daily M2 build.  
 
**If there are critical bugs that need to go into M1 during the 2-week rampdown period, we will branch based on the M1 tags for those critical fixes.
 
**If there are critical bugs that need to go into M1 during the 2-week rampdown period, we will branch based on the M1 tags for those critical fixes.
**The 1.6.1 M1 build will then be released and available as both download zips and on a corresponding update site on August 7.
+
**The 1.6.1 M1 build will then be released and available as both download zips and on a corresponding update site on '''August 7'''.
 
*Updated plan for 1.6.1 M2 release and 1.6.1 final release in September
 
*Updated plan for 1.6.1 M2 release and 1.6.1 final release in September
 
* '''August 25 (Monday):''' DTP 1.6.1 M2 Build
 
* '''August 25 (Monday):''' DTP 1.6.1 M2 Build

Revision as of 08:54, 21 July 2008

Back to DTP PMC and Project Lead Meeting page

Attendees

  • Brian Fitzpatrick
  • Larry Dunnell
  • Hung Hsi
  • Brian Payton
  • Linda Chan
  • John Graham
  • Sheila Sholars
  • Emily Kapner
  • Der Ping Chou

Regrets

Agenda

  • Updated plan for 1.6.1 M1 release
    • We will use the July 25 build as the 1.6.1 M1 milestone build.
    • Though there will be a 2 week rampdown and testing period for M1, committers can continue to develop into the HEAD branch for the daily M2 build.
    • If there are critical bugs that need to go into M1 during the 2-week rampdown period, we will branch based on the M1 tags for those critical fixes.
    • The 1.6.1 M1 build will then be released and available as both download zips and on a corresponding update site on August 7.
  • Updated plan for 1.6.1 M2 release and 1.6.1 final release in September
  • August 25 (Monday): DTP 1.6.1 M2 Build
  • September 1 (Monday): DTP 1.6.1 Release Candidate 1 (RC1) Build
  • September 2 (Tuesday) through September 5 (Friday): Testing & Fix Pass
    • Committers must annotate bugs proposed for inclusion in 1.6.1 with risks and nature of fix
    • Committers must get modifications reviewed by one other committer on project
    • Committers must petition team lead using BZ for inclusion of specific bugs
  • September 8 (Monday): DTP 1.6.1 Release Candidate 2 (RC2) Build
  • September 9 (Tuesday) through September 10 (Wednesday): Testing & Fix Pass
    • Committers must annotate bugs proposed for inclusion in 1.6.1 with risks and nature of fix
    • Committers must get modifications reviewed by one other committer on project
    • Committers must petition DTP PMC using BZ for inclusion of specific bugs
    • Two positive PMC votes allows modifications to fix a specific bug to be delivered
  • September 12 (Friday): Last possible DTP 1.6.1 Build
  • September 24 (Friday): DTP 1.6.1 Release
  • Platform Release Train Dates
    • RC1 - September 2, 2008, with EPP on Sept 8, Server freeze on Sept 9, and public access on Sept 10
    • RC2 - September 9, 2008, with EPP on Sept 15, Server freeze on Sept 16, and public access on Sept 17
    • Ganymede SR1 - September 15, 2008, with EPP on Sept 22, Server freeze on Sept 23, and public access on Sept 24
  • Request for a scrubbing pass through Bugzilla
    • Bugs typically fall into three categories - No Target Milestone, with a Target Milestone set, and set to Future
    • We want to go back to all bugs set for previous releases (0.7, 0.9, 1.0, 1.5 and their related maintenance version #s) and see if the bugs are still appropriate.
    • If appropriate to Ganymede and forward, work on it for the maintenance release or save for the next major release.
    • If things have changed (i.e. UI or API) to make the bug not an issue any more, set to a resolution of "Obsolete"
    • If it might be valid, but we're not looking to fix it in the maintenance release of by June of next year, set to a resolution of "Won't Fix"
    • Remember to add a tag of "helpwanted" if there's a bug you run across that is still valid, but we're not planning on fixing unless we get some additional help for it.
    • Goal here is to reduce the bug count, but provide meaningful response back to the reporter to let them know why the status has changed
  • We are at 30+ bugs with no target milestone set that need to be dispositioned. Please keep at this list daily if at all possible. [Here's the query.]
  • Sub-project status (from team leads)
  • Open discussion

Minutes

  • Will discuss 1.6.1 milestone/early release at PMC meeting tomorrow.

Action Items