Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
DTP PMC Meeting, January 27, 2009
← Back to DTP PMC Meeting Page
Attendees
- Brian Fitzpatrick
- Linda Chan
- John Graham
- Brian Payton
Regrets
Agenda
- Releng discussion
- Possible plan: Xiaoying already has commit rights on every DTP project except incubator
- If we elect her as a committer in the Incubator project, and move the map files + features to each respective project, she could still work on them
- And all committers on each project would have access to the releng + features for their respective projects by default
- This will require some changes to the build process Xiaoying has in place as well as electing her as a committer to the Incubator project, but it has the smallest amount of impact to the community at large
- Possible plan: Xiaoying already has commit rights on every DTP project except incubator
- Webinar
- After speaking to Lynn Gayowski (Eclipse Marketing), she said the following: "The goal is to provide a technical resource. Ultimately, it may increase awareness of the project, but attendees are generally looking for technical demos."
- Duncan is going to come up with an initial cut of a demo script and then ask Linda & Brian P for input
- Open discussion
Minutes
- Releng discussion
- Possibly may make using the release engineering tool difficult, but only for doing cross-sub-project deliveries which is only done occasionally
- Possibly clean out access to the releng folder after these changes go into effect, so only build folks have access
- Concerns about moving features - do we really want committers changing them? possibly just move map files
- Possibly do a cleanup in the features directory
- We have a workable plan to take to Xiaoying next week after Chinese New Year
- Reminded to tag the table wizard in the 1.6.2 branch now that I restored it (done)
- Work with the backward incompatibility continuing with Hemant
- Possibly find a way to support both EMF 2.4 and 2.5
- Possibly continue to support DTP 1.6 in a 1.6.3 release after 1.6.2
- Possibly have two different versions of DTP 1.7, one with a modelbase tailored for EMF 2.4, and one tailored for EMF 2.5 - this would then force users to know which version to download, but we'd have a couple of options for them
- Need to verify common navigator changes in 3.5 (Fitz)