Project Plan For TENEO [Teneo], version 1.5

This document lays out the planned features for the next major release of the model-driven Object Relational Mapping Framework Teneo, version 1.5. This project plan inherits from the Modeling Project Plan, which should be referenced when consulting this individual project plan.

The release deliverables have the same form as is found in most Eclipse projects, namely:

• Teneo SDK (includes Mapping Providers for different ORM Tools, Examples, Documentation and Source).
• Teneo Examples (contains the Teneo examples models and tutorials.
• Teneo Tests (contains the testcases).

Release milestone occurring at roughly 6 week intervals and follow the Platform milestone releases by approximately 1 week; that is, until the final 3.5 release of the Platform, upon which Teneo and other projects will release simultaneously. Teneo will deliver its milestones within one week of the Eclipse Platform. It is anticipated that Teneo will synchronize its milestones with the Galileo milestone schedule.

Teneo will produce maintenance releases to align with the Ganymede SR releases, that includes the Eclipse Platform 3.4.2 release. Teneo will have weekly Maintenance releases to solve any issues reported in the previous week. Maintenance releases are only done if there are issues to solve.

In order to remain current, each Eclipse release targets reasonably current versions of the underlying operating environments. The Teneo Project depends upon on the Platform and other projects, which are mostly "pure" Java^TM. Teneo will target the same Java version as EMF Core, which currently requires Java 5. Eclipse Platform SDK 3.5 will be tested and validated on a number of reference platforms. Teneo will be tested and validated against a subset of those listed for the platform.

Teneo is a runtime technology, most of the components having no user interface. The remaining user interface parts of Teneo are considered exemplary and thus no attention has been paid to externalize them for internationalization.

Teneo will add support for new ORM tools in the next release. Teneo will be backward compatible for the ORM tools supported in previous releases. Mapping stability/backward compatibility (generated the same mapping in new releases) is in this respect far more important than binary compatibility.

A list of project requirements 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 to be concentrated on for each. These themes are presented below, while the requirements document and associated Bugzilla entries are left to those wanting more detailed information on each.

The main theme for the upcoming release of Teneo is support for two new ORM Tools: EclipseLink and DataNucleus.

The Teneo project has a proven track record of quality, reliability, and extensibility but all these aspects can be continuously improved. Existing and new clients often desire more functionality from the framework while long established clients generally desire mostly improvements in performance. Often these two are at odds since additional extensibility often has a performance cost and any changes, even performance boosting ones, potentially impact reliability. Every effort will be made to introduce new capabilities so that they have negligible impact on established clients based on the guiding principle: if you don't use it, you don't pay for it. 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!

• 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.