Difference between revisions of "DTP PMC Meeting, June 3, 2008"
(New page: ← Back to DTP PMC Meeting Page ==Attendees== *Brian Fitzpatrick *Linda Chan *Sheila Sholars *John Graham ==Regrets== ==Agenda== *Branching/timing - after RC4? *...) |
(→Agenda) |
||
| Line 9: | Line 9: | ||
==Agenda== | ==Agenda== | ||
| − | |||
*Maintenance release dates? 1.6.1 - Wednesday September 24 - September/Fall release, and 1.6.2 - Wednesday February 25 - February/Winter release - ok with everybody? | *Maintenance release dates? 1.6.1 - Wednesday September 24 - September/Fall release, and 1.6.2 - Wednesday February 25 - February/Winter release - ok with everybody? | ||
| + | *Branching/timing - after RC4? | ||
*Moving to Subversion? Technical advantages? | *Moving to Subversion? Technical advantages? | ||
**Standard folder structure to help with common builds? | **Standard folder structure to help with common builds? | ||
Revision as of 16:28, 2 June 2008
← Back to DTP PMC Meeting Page
Attendees
- Brian Fitzpatrick
- Linda Chan
- Sheila Sholars
- John Graham
Regrets
Agenda
- Maintenance release dates? 1.6.1 - Wednesday September 24 - September/Fall release, and 1.6.2 - Wednesday February 25 - February/Winter release - ok with everybody?
- Branching/timing - after RC4?
- Moving to Subversion? Technical advantages?
- Standard folder structure to help with common builds?
- Accessibility assessment
- Open discussion
Minutes
Action Items
- New dependencies need to be approved, especially those across other projects, orbit, 3rd party, or whatever
Tabled for Later Discussion
- Discuss after Ganymede release
- Discuss DTP charter change to simplify addition of a committer to two or more subprojects at the same time without going through separate committer elections
- Perhaps in the future come up with a Component architecture document that shows DTP dependencies to consumers
- Schedule a "scrubbing" pass of the bug backlog after 1.6 (over the summer) to close bugs that we won't ever fix (minor tweaks, things that have been obsoleted along the way, etc.) to try and reduce the bug count