blob: 57e723f8eedac9418e2ccd0ca5d5ffaaed869301 [file] [log] [blame]
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<?xml-stylesheet type="text/xsl" href=""?>
<plan plan-format="1.0" xmlns="" xmlns:html=""
name="MDT XSD">
<release projectid="modeling.emf.emf" version="2.5.0"/>
<div xmlns="">
This document lays out the feature and API set for the
2.5.0 release of the Model Development Tools XML Schema Definition (MDT XSD) project.
This project plan inherits from the <a href="">Modeling Development Tools Project Plan</a>,
which should be referenced when consulting this individual project plan.
<div xmlns="">
The release deliverables have the same form as is found in most Eclipse projects, namely:
MDT XSD Core source code release,
available as versions tagged with "R2_5" in the project's CVS repository.
which includes runtime, sources, examples, and documentation,
and is available as a download or on the update site.
MDT XSD runtime binary distribution,
available as a download or on the update site.
MDT XSD as part of EMF's Core tests
available as a download.
<div xmlns="">
Release milestones occur at roughly 6 week intervals
and follow the Platform release milestone by the Galileo-established +1 delta interval,
though all effort will be made to reduce this to +1 business day
regardless of the size of the established +1 delta interval..
The final MDT XSD 2.5 release will available simultaneously
with the 3.5 release of the Platform and all the other Galileo projects.
It is anticipated that MDT XSD will synchronize its milestones
with any changes to the Galileo milestone schedule.
<milestone date="08/13/2008" milestone="M1"></milestone>
<milestone date="09/24/2008" milestone="M2"></milestone>
<milestone date="11/05/2008" milestone="M3"></milestone>
<milestone date="12/17/2008" milestone="M4"></milestone>
<milestone date="02/03/2009" milestone="M5"></milestone>
<milestone date="03/16/2009" milestone="M6"><div xmlns="">API freeze</div></milestone>
<milestone date="05/04/2009" milestone="M7"><div xmlns="">Feature Freeze</div></milestone>
<milestone date="05/18/2009" milestone="RC1"></milestone>
<milestone date="05/25/2009" milestone="RC2"></milestone>
<milestone date="06/01/2009" milestone="RC3"></milestone>
<milestone date="06/08/2009" milestone="RC4"></milestone>
<milestone date="06/15/2009" milestone="RC5"></milestone>
<milestone date="06/28/2009" milestone="2.5.0"></milestone>
<div xmlns="">
XSD MDT will produce maintenance releases to align with the Ganymede Service Releases
which includes the Eclipse Platform's 3.4.1 and 3.4.2 releases.
XSD MDT may produce additional interim maintenance releases.
Maintenance releases will only be published if they contain new fixes.
Monday, August 25, 2008 - MDT XSD 2.4.1 maintenance release
Friday, September 26, 2008 - MDT XSD 2.4.1 maintenance release for Ganymede Service Release 1.
Friday, February 27, 2009 - MDT XSD 2.4.2 maintenance release for Ganymede Service Release 2.
Version numbers are subject to change should there be be any additional maintenance releases.
A list of the issues addressed for the 2.4.x maintenance stream
are available in the <a href=";version=2.4.x">2.4.x release notes</a>.
<div xmlns="">
In order to remain current,
each Eclipse release targets reasonably current versions of the underlying operating environments.
The MDT XSD depends upon on the Platform,
which is mostly "pure" Java™.
The 3.5 release of the Eclipse Platform Project
is written and compiled against version 1.4 of the Java Platform APIs,
and targeted to run on version 1.4 of the Java Runtime Environment, Standard Edition.
with its runtime support for generics,
relies on Java 5.
Eclipse Platform SDK 3.5 will be tested and validated on a number of reference platforms.
MDT XSD will be tested and validated against a subset of those listed for the platform.
Given that there is no operating system dependent code in MDT XSD,
it's expected that MDT XSD will work anywhere the Eclipse Platform does.
<div xmlns="">
The Eclipse Platform is designed as the basis for internationalized products.
The user interface elements provided by the Eclipse SDK components,
including dialogs and error messages,
are externalized.
The English strings are provided as the default resource bundles.
Similarly, the MDT XSD project will externalize all its user interface elements,
provide English strings for them in its default bundles,
and localize a subset of the locales offered by the Platform.
The download page will provide the details as the become available.
<div xmlns="">
Compatibility of Release 2.4:
The XSD MDT project will be developed in parallel,
and released simultaneously,
with the following projects:
Eclipse Platform SDK version 3.5
Eclipse Modeling Framework Core SDK version 2.5
Each milestone version of the MDT XSD project
will be compatible with the corresponding milestone for these projects
and will be delivered within the appropriate time offset.
The ultimate MDT XSD release will be compatible with the released version of its dependencies
and will publish binary and source compatibilities with migration guides on subsequent releases.
<div xmlns="">
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.
<theme name="Service, Support, and Maintenance">
<div xmlns="">
The MDT XSD project has a proven track record of quality and reliability.
Because service and support has and always will take priority over new development work,
development commitments and schedules are subject to arbitrary change, slippage, or even deferral.
Be sure to establish direct communication to ensure that any hard commitments
are seen as that by the development team itself!
We expect little o4 no development work for the coming release.
<appendix name="Legal Notices">
<div xmlns="">
Java is a trademark or a registered trademark of Sun Microsystems, Inc.
All other products or company names are mentioned for identification purposes only,
and may be trademarks or service marks of their respective owners.