← Back to DTP PMC Meeting Page
- Brian Fitzpatrick
- Linda Chan
- John Graham
- Sheila Sholars
- The early release question (Loic's 184.108.40.206 request)
- Setting up a "scrubbing" pass during the maintenance release
- Planning for next major release
- Open discussion
- Discussed the Bugzilla "scrubbing" pass we're going to ask team leads and committers to start next week
- 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.
- Discussed the early or off-cycle patch/release requested by Loic & IBM.
- Want to keep criteria generic so we don't paint ourselves into a corner going forward.
- Criteria includes:
- Number of bugs/patches and quality/severity of bugs. A small number may not warrant a release, but if it's one major bug (like the Data Source Explorer not functioning) it would warrant a fix.
- Who's requesting the early/off-cycle release? If it's someone or an organization who's been very active in the community, that would most likely be considered over a request from someone who's been relatively quiet in the community.
- Who's going to "pay" for the release with respect to actually doing the work and then testing?
- When is the release requested for? Is it near an already planned release? Or does it fall between releases, such as between the February (SR2) maintenance release and the June release?
- How will the early/off-cycle release be distributed? Via download zips or an update site?
- John mentioned he had checked on the JBoss/Red Hat ODA driver and not received very favorable information about donating it back to DTP due to issues of a political nature at Eclipse rather than technical concerns.
- Hold off on RC milestones for 1.6.1 unless we get a better understanding of why we might need them
- New dependencies need to be approved, especially those across other projects, orbit, 3rd party, or whatever - need to write up as part of the DTP policies and procedures
- Need to add some policy regarding extension point documentation. Declare that if new extension points are added, they must have documentation by the mid-point milestone.
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
- Things to consider for next major release (June 2009) - JDK 1.4 end of life, move to JDK 1.5 in next release? Depends on platform support. Something to discuss going forward