Difference between revisions of "Equinox p2 M1"
m |
|||
| Line 5: | Line 5: | ||
* what scenarios, what can you do with M1, what can you NOT do? | * 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, ...) | * context for the UI (admin UI, not representative of the intended end user workflows, ...) | ||
| + | * where to enter bugs/make comments/... | ||
For more information see: | For more information see: | ||
Revision as of 16:41, 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, ...)
- where to enter bugs/make comments/...
For more information see: