project-info/plan.xml

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<?xml-stylesheet type="text/xsl" href="http://www.eclipse.org/projects/project-plan.xsl"?>
<plan plan-format="1.0" xmlns="http://www.eclipse.org/project/plan"
	xmlns:html="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xsi:schemaLocation="http://www.eclipse.org/project/plan http://www.eclipse.org/projects/plan.xsd"
	name="Sphinx">
	<release projectid="modeling.sphinx" version="0.8.0" />
	<introduction>
		<html:div>
			<html:p>
				Sphinx is an open source project under the
				<html:a href="http://www.eclipse.org/modeling">Eclipse Modeling</html:a>
				project to provide an extensible platform that eases the
				creation of integrated modeling tool environments supporting
				individual or multiple modeling languages (which can be UML-based or
				native DSLs) and has a particular focus on industrial strength and
				interoperability.
			</html:p>
			<html:p>
				This document lays out the feature and API set for the Sphinx
				release 0.8.0.
				Comments on this plan can be can
				be posted on
				<html:a
					href="http://www.eclipse.org/forums/index.php?t=thread&amp;frm_id=171">the forum</html:a>
				or sent to
				<html:a href="https://dev.eclipse.org/mailman/listinfo/sphinx.dev">the mailing list</html:a>
				.
			</html:p>
		</html:div>
	</introduction>
	<release_deliverables>
		<html:div>This release will be delivered via a p2 repository including
			SDK (runtime, sources and documentation), non-SDK (runtime only),
			examples and test utilities.
		</html:div>
	</release_deliverables>
	<release_milestones>
		<preamble>
			<html:div>
				Sphinx milestones follow the Eclipse release milestones by
				an offset of +3 as set by the
				<a href="http://wiki.eclipse.org/Luna#Milestones_and_Release_Candidates">Kepler release schedule.</a>
				This table lists all completed milestones and planned releases:
			</html:div>
			<html:p></html:p>
		</preamble>
		<milestone milestone="M3" date="11/20/2013"></milestone>
		<milestone milestone="M4" date="12/25/2013"></milestone>
		<milestone milestone="M5" date="02/05/2014"></milestone>
		<milestone milestone="M6" date="03/19/2014"></milestone>
		<milestone milestone="M7" date="05/14/2014"></milestone>
		<milestone milestone="RC1" date="05/28/2014"></milestone>
		<milestone milestone="RC2" date="06/04/2014"></milestone>
		<milestone milestone="RC3" date="06/11/2014"></milestone>
		<milestone milestone="RC4" date="06/18/2014"></milestone>
		<milestone milestone="0.8.0 Final" date="06/25/2014"></milestone>
	</release_milestones>
	<target_environments>
		<html:p>
			The Sphinx 0.8 targets a defined set of other Eclipse components
			(e.g. platform, EMF, etc.) originating from the following release
			trains:
			<html:ul>
				<html:li>Kepler (Eclipse 4.3)</html:li>
				<html:li>Luna (Eclipse 4.4)</html:li>
			</html:ul>
		</html:p>
		<html:p>
			Sphinx builds and testing will always be based on latest
			available milestone build or service release of Eclipse (e.g. Eclipse
			4.4M3, 4.4.1).
		</html:p>
		<html:p>
			Sphinx will work with Java 5 or higher.
		</html:p>
		<internationalization>
			<html:p>
				The Sphinx plug-ins are prepared for internalization using
				the usual Eclipse plugin.properties mechanism. Default language is
				English. Currently no other translations exist.
			</html:p>
		</internationalization>
	</target_environments>
	<themes_and_priorities>
		<preamble>
			<html:div>
				A list of project goals and agreed upon implementation time
				frames is found in this document. For the milestones listed in this
				document, a set of overall themes is used to indicate what major set
				of functionalities is expected to be the focus of each. These themes
				are presented below, while the goals of the associated Bugzilla
				entries are available for more detailed information.
			</html:div>
		</preamble>
		<theme name="Reusability, Interoperability and Performance">
			<description>
				<html:div>
					<html:p>
						Initially driven by automotive functionality as such is
						generic and the Sphinx is meant to enable the reuse of this
						infrastructure for model-driven tool environments in others
						domains
						like aerospace, finance, etc.
					</html:p>
					<html:p>
						Thus, the interoperability of sereral model-driven tool
						environments
						based on different Domain-Specific Languages (DSLs) will be facilitated by the
						Sphinx platform.
					</html:p>
					<html:p>
						Sphinx already includes many optimizations to improve the
						runtime
						performance when it comes to handling and processing bigger
						models
						(e.g., file content type detection, model loading or
						unloading).
						Nevertheless, further and potentially quite significant
						performance
						improvements could be achieved by introducing a model
						indexing
						service in Sphinx and using index-backed queries to
						perform
						runtime-intensive operations on EMF models (e.g., proxy
						resolution,
						model validation, deletion of model elements).
					</html:p>
				</html:div>
			</description>
		</theme>
	</themes_and_priorities>
	<!-- <compatibility_with_previous_releases> -->
	<!-- <html:div>Version 2.3 will be binary compatible with the Xtext version -->
	<!-- 2.0, 2.1 and 2.2. This means languages developed and compiled against -->
	<!-- 2.0, 2.1 and 2.2 will work with 2.3 without recompilation. -->
	<!-- </html:div> -->
	<!-- </compatibility_with_previous_releases> -->
</plan>