Skip to main content
Jump to: navigation, search

Difference between revisions of "Equinox p2 M1"

Line 1: Line 1:
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.
+
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 on what scenarios you can do with M1
 +
- set expectations here
 +
'''
 
For more information see:
 
For more information see:
 
* [[Equinox Provisioning Getting Started#Getting Started with M1 | Getting started with M1]]
 
* [[Equinox Provisioning Getting Started#Getting Started with M1 | Getting started with M1]]
 
* [[Equinox Provisioning RCP Agent Users Guide]]
 
* [[Equinox Provisioning RCP Agent Users Guide]]
 
* [[Equinox Provisioning Tips n Tricks]]
 
* [[Equinox Provisioning Tips n Tricks]]

Revision as of 15:31, 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 on what scenarios you can do with M1 - set expectations here For more information see:

Back to the top