Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 350464

Summary: Juno plan
Product: [Eclipse Project] Platform Reporter: John Arthorne <john.arthorne>
Component: PMCAssignee: John Arthorne <john.arthorne>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: P3 CC: daniel_megert, Mike_Wilson, pwebster, remy.suen, thatnitind
Version: 3.7   
Target Milestone: 4.2   
Hardware: PC   
OS: Windows 7   
Whiteboard:

Description John Arthorne CLA 2011-06-27 11:46:46 EDT 
I have started a draft Juno (4.2) plan here:

http://www.eclipse.org/projects/project-plan.php?planurl=http://www.eclipse.org/eclipse/development/plans/eclipse_project_plan_4_2.xml

We need to collect plan items over the coming weeks.
Comment 1 Dani Megert CLA 2011-07-04 09:12:48 EDT 
Do we create a separate 3.8 plan? I guess we should.
Comment 2 Dani Megert CLA 2011-07-04 09:14:33 EDT 
> Do we create a separate 3.8 plan? I guess we should.
If not, we need to tag the special 3.8 items in the 4.2 plan and have a different lists for 'Appendix Execution Environment by Bundle'.
Comment 3 Mike Wilson CLA 2011-07-05 16:49:55 EDT 
My preference would be to build a single plan that indicates what we are going to do in 4.2. 

If we were build a 3.8 plan, it's main theme would have to be "Stability and platform currency", with the one addendum that some set of the plan items from 4.2 may appear in 3.8 if they can be implemented in a way that does not run counter to the theme.

To be clear, just because it might be *possible* to implement a particular work item in a way that would allow it to run on both 3.8 and 4.2, does not imply that we should necessarily release it into 3.8. We would be doing this on a case-by-case basis, based on the potential impacts (both positive and negative) on our consumers.