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 and Project Lead Meeting Minutes: February 9, 2009"
(New page: ← Back to DTP PMC and Project Lead Meeting page ==Attendees== *Brian Fitzpatrick *Linda Chan *Larry Dunnell *Hung Hsi *John Graham *Brian Payton...) |
(→Agenda) |
||
| Line 14: | Line 14: | ||
==Agenda== | ==Agenda== | ||
| − | * [ | + | * Reminder of what goes in maintenance releases (bug releases like 1.6.2) vs. regular releases (1.7) |
| + | **According to the Eclipse Development Guidelines (here[http://www.eclipse.org/projects/dev_process/development_process.php#6_4_Releases])... | ||
| + | ***Bug fix releases (x.y.z, e.g., 2.3.1) with no new features over the base release (e.g., 2.3) are allowed to be released without an additional Release Review. If a bug fix release contains new features, then the Project must have a full Release Review. | ||
| + | **When submitting bugs for inclusion in a maintenance release, we must keep the question in mind whether the bug is truly a bug fix or adds new features. If it's a critical BUG fix, we're good with voting on it at the PMC level and seeing if it should appear in 1.6.2. Otherwise, it needs to only go in Galileo (1.7). | ||
* Status | * Status | ||
| − | * [Weekly Nag] We are at ~ | + | * [Weekly Nag] We are at ~10 bugs with no target milestone set that need to be dispositioned. Great work! This has been cut in half since last week. Please keep at this list daily if at all possible. [http://tinyurl.com/6robrj[Here's the query.]] |
* Open discussion | * Open discussion | ||
Revision as of 11:26, 9 February 2009
← Back to DTP PMC and Project Lead Meeting page
Contents
Attendees
- Brian Fitzpatrick
- Linda Chan
- Larry Dunnell
- Hung Hsi
- John Graham
- Brian Payton
- Emily Kapner
- Hemant Kolwalkar
Regrets
Agenda
- Reminder of what goes in maintenance releases (bug releases like 1.6.2) vs. regular releases (1.7)
- According to the Eclipse Development Guidelines (here[1])...
- Bug fix releases (x.y.z, e.g., 2.3.1) with no new features over the base release (e.g., 2.3) are allowed to be released without an additional Release Review. If a bug fix release contains new features, then the Project must have a full Release Review.
- When submitting bugs for inclusion in a maintenance release, we must keep the question in mind whether the bug is truly a bug fix or adds new features. If it's a critical BUG fix, we're good with voting on it at the PMC level and seeing if it should appear in 1.6.2. Otherwise, it needs to only go in Galileo (1.7).
- According to the Eclipse Development Guidelines (here[1])...
- Status
- [Weekly Nag] We are at ~10 bugs with no target milestone set that need to be dispositioned. Great work! This has been cut in half since last week. Please keep at this list daily if at all possible. [Here's the query.]
- Open discussion