Community
Participate
Working Groups
Create a draft plan for the Eclipse project's contribution to the Indigo simultaneous release.
You can view an initial draft of the plan here: http://www.eclipse.org/projects/project-plan.php?planurl=http://www.eclipse.org/eclipse/development/plans/eclipse_project_plan_3_7_DRAFT.xml
I like the hilevel themes (Platforms, Robustness, Ease of use). For robustness, a security discussion comes to mind (bug 324223 comment 5), and recent discussions about a "hotpatching" infrastructure (triggered by bug 319514). Other than that, I noticed - Release Deliverables. I thought we had some discussion about reducing the size of Eclipse Downloads, by using fewer runnables but more archived p2 repo. The JDT and PDE runnables could probably be removed, for instance. - Reference Platforms. Always interesting :) The Multi-touch plan item refers to OSX 10.6 but we only list OSX 10.5 as a Reference Platform? Can/shall we really claim HP-UX as a reference platform?
There's already a 3.7 plan published: http://www.eclipse.org/projects/project-plan.php?projectid=eclipse ==> It would be good to mark the interesting changes as usual. The BREE (Appendix) for org.eclipse.jdt.ui org.eclipse.jdt.junit needs to be changed to '1.5'. Same for ICU if the PMC approves this move.
(In reply to comment #3) > There's already a 3.7 plan published: > http://www.eclipse.org/projects/project-plan.php?projectid=eclipse > ==> It would be good to mark the interesting changes as usual. Done, for next draft I am about to push out. > The BREE (Appendix) for > org.eclipse.jdt.ui > org.eclipse.jdt.junit > needs to be changed to '1.5'. Same for ICU if the PMC approves this move. I have a tool that computes this section automatically from a given build. I ran it against the M2 candidate, so the org.eclipse.jdt.junit BREE has been updated. org.eclipse.jdt.ui still appears to be using 1.4, but if it changes I can catch that on the next plan update.
(In reply to comment #2) > I like the hilevel themes (Platforms, Robustness, Ease of use). For robustness, > a security discussion comes to mind (bug 324223 comment 5), and recent > discussions about a "hotpatching" infrastructure (triggered by bug 319514). Something might come up there, if the Foundation comes out with a policy about handling them. Currently there is nobody signed up to work in that area, hence no plan item. > - Release Deliverables. I thought we had some discussion about reducing the > size of Eclipse Downloads, by using fewer runnables but more archived p2 > repo. The JDT and PDE runnables could probably be removed, for instance. Good point. That has already been done but the plan was never updated. I have updated the list to refer to downloadable repositories rather than runable binaries. > - Reference Platforms. Always interesting :) The Multi-touch plan item refers > to OSX 10.6 but we only list OSX 10.5 as a Reference Platform? Can/shall > we really claim HP-UX as a reference platform? We have somebody here who does regular testing on HP-UX so I think that one is ok. I'll look into upgrading the OS X version - I need want to check what the SWT developers are using, what the test machine is using, etc.
I have released a new draft plan, same link as comment #1. There are two additional plan items based on feedback from component teams: - resource filter enhancements - Webkit support on Windows
Some small reference platform updates after talking to Silenio about SWT plans for the year: - Replace AIX Motif 32-bit with AIX GTK 64-bit - Drop Mac Carbon as a reference platform - Move Mac OS X to 10.6 as suggested by Martin
Plan has been posted here: http://www.eclipse.org/projects/project-plan.php?planurl=http://www.eclipse.org/eclipse/development/plans/eclipse_project_plan_3_7.xml
