Difference between revisions of "DTP PMC and Project Lead Meeting Minutes: April 7, 2008"

From Eclipsepedia

Jump to: navigation, search
(Action Items)
 
Line 1: Line 1:
 +
←[[DTP PMC and Project Lead Meeting | Back to DTP PMC and Project Lead Meeting page]]
 +
 
==Attendees==
 
==Attendees==
 
*Brian Fitzpatrick
 
*Brian Fitzpatrick

Latest revision as of 13:51, 14 April 2008

Back to DTP PMC and Project Lead Meeting page

Contents

[edit] Attendees

  • Brian Fitzpatrick
  • Sheila Sholars
  • Brian Payton
  • Linda Chan
  • Larry Dunnell

[edit] Regrets

  • John Graham
  • Der-Ping Chou
  • Hung Hsi

[edit] Agenda

  • DTP PMC Chair transition
  • DTP 1.6M6 status
  • To avoid last-minute regressions as we've seen at the end of M6, the PMC has decided to implement a new test period before declaring milestones. Since release candidates are subject to the Rampdown Policy, we're only concerned about DTP 1.6M7 here. The new policy is:
    • Commits for M7 will be allowed through the build start time on Tuesday, April 29th by 1:30pm PST
    • The testing period will start on April 30 and last through May 2 to be ready to push up to the site on May 5.
    • Committers wishing to include additional bug fixes in M7 between April 30 and May 2 must provide the following in an associated Bugzilla entry:
      • Document the severity and impact of the bug: why should this be included in the milestone at such a late date?
      • Document the proposed resolution, risk, and validation testing that will occur
      • Petition the DTP PMC for permission to deliver the change to the build. At least two (2) of the four (4) PMC members must approve, with no PMC member objecting, for the bug to be authorized for the M7 build.
  • Review of bugs with no target milestone set.
  • Open discussion

[edit] Minutes

  • Updated M7 policy with more specific date/time for delivery cutoff

[edit] Action Items

  • Check to see if expectations for milestones have been set in other documents published for DTP -- Sheila mentioned that we'd been going with the general plan that M6 indicated API freeze and M7 indicated feature freeze.
  • Send out note to mailing lists, newsgroups about new M7 policy
  • Add updated M7 policy to Ganymede project plan page
  • Asked folks to take a look at BZ entries without milestones to start setting them for M7 or future as necessary