Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Equinox p2 M1"
m |
|||
Line 1: | Line 1: | ||
Milestone 1, as the name implies, is our first step towards a [[Equinox Provisioning | new provisioning system for Eclipse]]. We have hit most of the major items on the [[Equinox Provisioning Plan#M1.2C August 2nd | M1 plan ]]except for roll-back support. The meta-goal of M1 was to ''self-provision''. That is, use the new provisioning support to install and manage the Eclipse environment that we ourselves use to write the provisioning system. | Milestone 1, as the name implies, is our first step towards a [[Equinox Provisioning | new provisioning system for Eclipse]]. We have hit most of the major items on the [[Equinox Provisioning Plan#M1.2C August 2nd | M1 plan ]]except for roll-back support. The meta-goal of M1 was to ''self-provision''. That is, use the new provisioning support to install and manage the Eclipse environment that we ourselves use to write the provisioning system. | ||
− | '''More information | + | '''More information here''' |
− | + | * set expectations | |
+ | * what scenarios, what can you do with M1, what can you NOT do? | ||
+ | * context for the UI (admin UI, not representative of the intended end user workflows, ...) | ||
For more information see: | For more information see: |
Revision as of 16:36, 2 August 2007
Milestone 1, as the name implies, is our first step towards a new provisioning system for Eclipse. We have hit most of the major items on the M1 plan except for roll-back support. The meta-goal of M1 was to self-provision. That is, use the new provisioning support to install and manage the Eclipse environment that we ourselves use to write the provisioning system.
More information here
- set expectations
- what scenarios, what can you do with M1, what can you NOT do?
- context for the UI (admin UI, not representative of the intended end user workflows, ...)
For more information see: