Xtend2 SDK (a domein-specific language for customizing all aspects of Xtext. Built with Xtext and based on Xbase. Includes runtime and tooling components, with sources, examples, and documentation) (downloadable and update site).

Release milestone occurring at roughly 6 week intervals and follow the Platform milestone releases by approximately 2 weeks;
that is, until the final 3.7 release of the Platform, upon which Xtext and other projects will release simultaneously.
Xtext delivers milestones synchronized with the Juno release schedule.

In order to remain current, each Eclipse release targets reasonably current versions of the underlying operating environments.
The Xtext project depends upon on the 3.5 (Galileo) release of the Eclipse Platform and other projects, and targets to run on
version 1.5 of the Java Runtime Environment, Standard Edition.

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.

Reusability

Xbase is a sophisticated language library, providing the power of full-blown expressions to any
Xtext-based language targeting the Java platform. In 2.3 it will be even simpler to implement JVM-based
domain-specific languages.

Increase Applicability

One of our guiding principles is "make common things easier and rare things possible" suggests that we focus on extensibility as well as
on simplicity with regards to all kinds of API. In Helios we want to allow Xtext to be used in more situations by providing an easy to reuse base language.

Performance and Scalability

Performance and scalability needs to be further enforced.

Clean Code

Keeping the quality of code high is key for long lasting software systems.
We want to further keep our code clean, which means doing things like removing dead code, cleaning up / rewriting code we do no longer understand,
avoiding redundancy, etc..