Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "DTP PMC Meeting April 1, 2008"
| Line 13: | Line 13: | ||
*Open discussion | *Open discussion | ||
==Minutes== | ==Minutes== | ||
| − | + | *Announcements from agenda | |
| + | *Test period before declaring milestones: In order to avoid last minute regressions like we've seen so far in M6, we should require that milestone work be completed early enough before the deadline so testing can occur. Since release candidates are subject to the [[DTP_Ganymede_Rampdown_Policy | Rampdown Policy]], we're only concerned about DTP 1.6M7 here. PMC agree to the following policy: | ||
| + | **Commits for M7 will be allowed through the [[DTP_Build_Transition | build start time]] on Tuesday, April 29th. | ||
| + | **Testing will occur between 4/30 through 5/2. | ||
| + | **Committers wishing to include additional bug fixes in M7 between 4/30 and 5/2 in an associated Bugzilla entry must: | ||
| + | ***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. | ||
==Action Items== | ==Action Items== | ||
Revision as of 16:49, 1 April 2008
← Back to DTP PMC Meeting Page
Contents
Attendees
- John Graham
- Brian Fitzpatrick
- Sheila Sholars
- Linda Chan
Regrets
Agenda
- Reminder: New conference call numbers for DTP meetings starting next week.
- General observation: it is somehow fitting that the last DTP meeting I conduct is on April Fools Day
- Welcoming Brian Fitzpatrick to the DTP PMC chair role
- Open discussion
Minutes
- Announcements from agenda
- Test period before declaring milestones: In order to avoid last minute regressions like we've seen so far in M6, we should require that milestone work be completed early enough before the deadline so testing can occur. Since release candidates are subject to the Rampdown Policy, we're only concerned about DTP 1.6M7 here. PMC agree to the following policy:
- Commits for M7 will be allowed through the build start time on Tuesday, April 29th.
- Testing will occur between 4/30 through 5/2.
- Committers wishing to include additional bug fixes in M7 between 4/30 and 5/2 in an associated Bugzilla entry must:
- 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.