Updated project plan.
diff --git a/project-info/plan.xml b/project-info/plan.xml
index 1e5056c..d46f118 100644
--- a/project-info/plan.xml
+++ b/project-info/plan.xml
@@ -2,15 +2,33 @@
<?xml-stylesheet type="text/xsl" href="http://www.eclipse.org/projects/project-plan.xsl"?>
<plan name="Agent Modeling Platform (Incubation)" plan-format="1.0"
xmlns="http://www.eclipse.org/project/plan" xmlns:html="http://www.w3.org/1999/xhtml">
- <release projectid="modeling.amp" version="1.0" />
+ <release projectid="modeling.amp" version="0.8.0" />
<introduction>
- <html:div>This plan is quite preliminary and will change. Also note
- that this plan somewhat ambitiously carries the project through to
- the initial 1.0 (non-incubation) release. Please note that as with
- all Eclipse Incubation projects, version numbers are 0.n. This does
- not necessarily reflect overall code completion or quality. For
- example 0.7.0 is planned to have a reasonably stable API and 0.8.+
- should (hopefully) be nearly production ready.</html:div>
+ <html:div>
+ We're making a major change to the schedule. Rather than
+ focus on
+ getting the new Acore meta-model out, we're working on
+ getting
+ documentation, testing and polish completed first so that we
+ have the
+ best possible platform for future improvements. MetaABM is
+ not
+ perfect, but it works very well for the majority of current use
+ cases. The greatest priority now is to build up a good user and
+ contributor base and that means using the current very stable
+ meta-model target and improving surrounnding infrastructure.
+ <p />
+ Please note that as with
+ all Eclipse Incubation projects, version
+ numbers are
+ 0.n. This is not a reflection of overall code completion
+ or quality. For
+ example 0.7.0 is planned to have a reasonably stable
+ API and 0.8.+ should be production ready, i.e. at least equivalent to
+ 1.0. The 0.9.0 release is the new target for Acore functionality,
+ though we may decide to do a 1.0.0 release first. This will depend on
+ our progress in building community, which looks really positive.
+ </html:div>
</introduction>
<release_deliverables>
<html:div xmlns="http://www.w3.org/1999/xhtml">
@@ -26,36 +44,46 @@
<release_milestones>
<preamble />
<milestone date="06/15/2009" milestone="0.0.0">
- <html:div>Initial AXF Commit. Basic repackaging / renaming. Move dependencies from oAW to
- M2T. AGF/AXF API Experimental. Escape Modeling API Frozen.</html:div>
+ <html:div>Initial AXF Commit. Basic repackaging / renaming. Move
+ dependencies from oAW to
+ M2T. AGF/AXF API Experimental. Escape
+ Modeling API Frozen.</html:div>
</milestone>
<milestone date="07/15/2009" milestone="M0">
- <html:div xmlns="http://www.w3.org/1999/xhtml">AMF Commit. AMF API and meta-model Experimental (To be replaced w/ acore). AGF/AXF API Experimental. Escape Modeling API Frozen.
+ <html:div xmlns="http://www.w3.org/1999/xhtml">AMF Commit. AMF API and meta-model
+ Experimental (To be replaced w/ acore). AGF/AXF API Experimental.
+ Escape Modeling API Frozen.
</html:div>
</milestone>
<milestone date="08/15/2009" milestone="Public Release">
- <html:div xmlns="http://www.w3.org/1999/xhtml">[Slip] Automated build and tests, update site, basic documentation.
+ <html:div xmlns="http://www.w3.org/1999/xhtml">[Slip] Automated build and tests, update
+ site, basic documentation.
</html:div>
</milestone>
<milestone date="1/1/2010" milestone="M1">
- <html:div xmlns="http://www.w3.org/1999/xhtml">0.5.0. Builds to Modeling project standards. Meets general eclipse
- quality standards. User getting started documentation. New testing and parameterization functionality. All APIs and meta-models Provisional.</html:div>
+ <html:div xmlns="http://www.w3.org/1999/xhtml">0.5.0. Builds to Modeling project standards.
+ Meets general eclipse
+ quality standards. User getting started
+ documentation. New testing and parameterization functionality. All
+ APIs and meta-models Provisional.</html:div>
</milestone>
- <milestone date="2/15/2010" milestone="M2">
- <html:div xmlns="http://www.w3.org/1999/xhtml">Introduction of acore meta-model -- improvements (generalization, features) to meta-model from
- MetaABM. All APIs and meta-models Provisional.</html:div>
+ <milestone date="4/20/2009" milestone="M2">
+ <html:div xmlns="http://www.w3.org/1999/xhtml">UI Polish. Complete parameterization,
+ testing and data extensions. Meta-Model Extensions.
+ AMF core
+ Platform, API meta-model Provisional, AXF/AGF API Provisional.
+ </html:div>
</milestone>
- <milestone date="3/31/2009" milestone="M3">
- <html:div xmlns="http://www.w3.org/1999/xhtml">Improvements to meta-model based on community feedback. UI Polish. Meta-Model Extensions.
- AMF core Platform, API meta-model Provisional, AXF/AGF API Provisional.</html:div>
+ <milestone date="5/31/2010" milestone="0.8.0 Release">
+ <html:div xmlns="http://www.w3.org/1999/xhtml">0.8.0 Feature frozen. QA, bug fixes,
+ internals and runtime improvements. All API and existing Meta-Models
+ Platform.</html:div>
</milestone>
- <milestone date="4/30/2010" milestone="M4">
- <html:div xmlns="http://www.w3.org/1999/xhtml">(This will likely slip.) Join 3.6 release train. QA, bug fixes, internals and
- runtime improvements.
- All API and Meta-Models Platform.</html:div>
- </milestone>
- <milestone date="5/31/2010" milestone="RC1">
- <html:div xmlns="http://www.w3.org/1999/xhtml">Features frozen. Bug fixes, minor internals.</html:div>
+ <milestone date="7/1/201" milestone="0.9.0 M1">
+ <html:div xmlns="http://www.w3.org/1999/xhtml">Introduction of acore meta-model --
+ improvements (generalization, features) to meta-model from
+ MetaABM.
+ All APIs and meta-models Provisional.</html:div>
</milestone>
<milestone date="06/15/2010" milestone="RC2"></milestone>
<milestone date="06/28/2010" milestone="1.0"></milestone>
@@ -71,17 +99,21 @@
</compatibility_with_previous_releases>
<themes_and_priorities>
<preamble>
- <html:div xmlns="http://www.w3.org/1999/xhtml">Please note that the below are goals, not advertisements.
- We might not meet all of them, but by keeping them in mind, AMP
+ <html:div xmlns="http://www.w3.org/1999/xhtml">Please note that the below are goals, not
+ advertisements.
+ We might not meet all of them, but by keeping them in
+ mind, AMP
contributors and users can focus their
- efforts on the important
+ efforts on the
+ important
stuff.</html:div>
</preamble>
<theme name="Innovative">
<description>
<html:div xmlns="http://www.w3.org/1999/xhtml">
<ul>
- Provide disruptive tools that support new ways of doing modeling
+ Provide disruptive tools that support new ways of doing
+ modeling
and general science.
</ul>
<ul>
@@ -100,7 +132,8 @@
Provide an API capable of supporting a full user experience.
</ul>
<ul>
- Provide comprehensive documentation, examples and exemplar usages.
+ Provide comprehensive documentation, examples and exemplar
+ usages.
</ul>
</html:div>
</description>
@@ -113,11 +146,14 @@
processes, including builds, testing and internal documentation.
</ul>
<ul>
- Use Eclipse approaches (e.g. adapters, extension points, OSGi and
+ Use Eclipse approaches (e.g. adapters, extension points, OSGi
+ and
other runtime
- mechanisms) to support extremely low coupling between
+ mechanisms) to support extremely low coupling
+ between
AMP
- components and for toolsets utilizing AMP. For example, as an
+ components and for toolsets utilizing AMP. For example,
+ as an
exemplar project the core Escape library and AMP will ideally
share no
common API.
@@ -151,12 +187,15 @@
audience.
</ul>
<ul>
- Build an open, welcoming and inclusive community of collaborators
- and committers by involving other projects, organizations, and
+ Build an open, welcoming and inclusive community of
+ collaborators
+ and committers by involving other projects,
+ organizations, and
scientific disciplines.
</ul>
<ul>
- Preserve a strong architectural vision, but be open to new ideas
+ Preserve a strong architectural vision, but be open to new
+ ideas
and approaches.
</ul>
</html:div>
