Location: http://www.eclipse.org/buckminster/project-info/project-plan.xml
Meta-data Tag: projectplanurl
Raw:

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<?xml-stylesheet type="text/xsl" href="http://www.eclipse.org/projects/project-plan.xsl"?>
<p:plan plan-format="1.0" xmlns:p="http://www.eclipse.org/project/plan"
	xmlns="http://www.w3.org/1999/xhtml" name="Buckminster">
	<p:release projectid="tools.buckminster" version="1.0" />
	<p:introduction>
		<div>Buckminster is a component resolution &amp; materialization framework. Its purpose is to get
     software components for you and materialize them in a context of choice, typically a workspace or
     file system. This applies whether you are looking at what's available on your local machine, within
     your development organization or in the public open source cloud. Buckminster reuses existing
     investments in a wide range of build and source management tools - Maven, ANT, CVS, SVN, PDE, etc.
     It removes ambiguity from component descriptions, enables component sharing and increases
     productiveness when applied in development, build, assembly and deploy scenarios. 
     </div>
   </p:introduction>
   <p:release_deliverables>
     <div>
     		Buckminster is made available in two major types of packaging:<ul>
		<li>
			<p><b>Eclipse Update Site</b> for regular use inside the Eclipse IDE</p><p>There
			are several features available. They are categorized into &#39;core&#39; and &#39;optional&#39;.
			Please note that you are expected to <u>make a choice</u> of what optional categories you need.
			Do <u>not</u> select all of them. Buckminsters support for Subversive and Subclipse
			in particular should be considered as mutually exclusive to one another.</p>
		</li>
		<li>
			<p><b>Headless Product</b> application based on the Eclipse Runtime. This
			product is aimed towards those who need to use Buckminster without using
			a User Interface - think automated scripting. It contains only the bare
			minimum to get a working headless command line utility. To make it useful,
			you are supposed to install the features <u>you</u> need into it, and the
			result can then be shared as necessary.</p>
			<p>Updating the Headless Product is performed by using a headless install command
			that in turn will use the Eclipse P2 to install features.</p>
		</li>
		<li>
		<p>The headless integrations for Subclipse and Subversion contains plug-ins has licenses which prohibits them from
		being redistributed from Eclipse.org. Instead, we distribute them from Cloudsmiths website. The update site can be
		found at <i>http://download.cloudsmith.com/buckminster/external</i>.
		</p>
		<p>More details about Buckminster downloads can be found at our <a href="http://www.eclipse.org/buckminster/downloads.html">download page</a></p>
		</li>
		</ul>
     </div>
   </p:release_deliverables>
   <p:release_milestones>
      <p:preamble>
         <div>      
<a name="m_release_milestones">Release milestones</a>
will be occurring at roughly 6 week intervals,
and will be aligned with the
<a href="http://wiki.eclipse.org/Galileo_Simultaneous_Release">
Galileo Simultaneous Release</a> train.
Milestone names start with M6 in order to clarify this
relationship.</div>
      </p:preamble>
      <p:milestone date="3/18/2009" milestone="M6"/>
      <p:milestone date="5/5/2009" milestone="M7"/>
      <p:milestone date="5/19/2009" milestone="RC1"/>
      <p:milestone date="6/16/2009" milestone="Final"/>
      <p:postamble><div>A detailed <a href="http://wiki.eclipse.org/Buckminster/Galileo_Ramp-Down_Policy">
Ramp down Plan</a> towards the release is available especially for the Eclipse 
<a href="http://wiki.eclipse.org/Galileo_Simultaneous_Release">
Galileo Simultaneous Release</a> integration.
</div></p:postamble>
   </p:release_milestones>
 </p:plan>