Community
Participate
Working Groups
For 4.0 we had http://www.eclipse.org/eclipse/development/plans/eclipse_project_plan_4_0.xml but for 4.1 I can't find a corresponding plan. If we plan to ship 4.1 then we need to have a plan similar to the previous plans that shows: - Release Deliverables - Release Milestones - Target Environments - Compatibility with Previous Releases - Themes and Priorities - Appendix (for all bundles, not just the 3.x ones)
Draft plan here: http://www.eclipse.org/projects/project-plan.php?planurl=http://www.eclipse.org/eclipse/development/plans/eclipse_project_plan_4_1.xml
The plan says: Workspace Compatibility: ... This means that workspaces and projects created with Eclipse SDK 4.0, 3.6 .. 3.0 can be successfully opened by Eclipse SDK 4.1 and upgraded to a 4.1 workspace... However, the migration support is only listed as proposed item and its corresponding bug 333105 only talks about migration from 4.0.
(In reply to comment #2) > Workspace Compatibility: ... This means that workspaces and projects created > with Eclipse SDK 4.0, 3.6 .. 3.0 can be successfully opened by Eclipse SDK 4.1 > and upgraded to a 4.1 workspace... > > However, the migration support is only listed as proposed item and its > corresponding bug 333105 only talks about migration from 4.0. Yes, but the plan also says, "User interface session state may be discarded when a workspace is upgraded." Since the *only* thing different between 3.7 and 4.1 is the UI state, I'm fairly confident we can achieve this. All we need to do is detect that we opened a workspace that does not have 4.1 version of UI state, and if so we discard it. From talking with Remy, that infrastructure seems to be mostly in place. There is some ongoing work involved to test this as the UI model evolves during the development cycle.
(In reply to comment #3) > (In reply to comment #2) > > Workspace Compatibility: ... This means that workspaces and projects created > > with Eclipse SDK 4.0, 3.6 .. 3.0 can be successfully opened by Eclipse SDK 4.1 > > and upgraded to a 4.1 workspace... > > > > However, the migration support is only listed as proposed item and its > > corresponding bug 333105 only talks about migration from 4.0. > > Yes, but the plan also says, "User interface session state may be discarded > when a workspace is upgraded." Since the *only* thing different between 3.7 > and 4.1 is the UI state, I'm fairly confident we can achieve this. All we need > to do is detect that we opened a workspace that does not have 4.1 version of UI > state, and if so we discard it. From talking with Remy, that infrastructure > seems to be mostly in place. There is some ongoing work involved to test this > as the UI model evolves during the development cycle. I was not arguing whether it's possible to do or not - just about the inconsistencies between the items (compatibility, plan item and bug report).
I published the 4.1 plan awhile ago but forgot to close this bug.
