Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »


Considering our limited human resources and time constraints, it is hard to give definitive and accurate estimates of the milestones we are going to release. Nevertheless, in the following sections, you can learn about the milestones we plan to deliver in the coming weeks.

Part of the JSR process, we must produce three key deliverables:

  • RI (Reference Implementation): The RI is the binary distribution of the Groovy Scripting Language which passes the TCK
  • TCK (Test Compatibility Kit): The TCK is a suite of tests, tools and documentation that determines whether or not a Groovy implementation (RI or third-party implementation) complies with the GLS.
  • GLS (Groovy Language Specification): The GLS defines the language's grammar and semantics.

Beta milestones

  • beta-9 (mid-january): Last "Groovy Classic" release which supports the JDK 5.0 platform as a running target.
  • beta-10 (mid-to-late-february): It will be the last beta release with the old parser, which will include mostly bug fixes, but also include an early access 'JSR Groovy' parser which will be usable via a configuration flag, so you can try out New Groovy. The markup / builder feature will probably be missing in this EA release of the new parser

JSR milestones

The naming scheme is changing to reflect the work done in the JSR process, and we will adopt the "jsr" tag.

  • jsr-1 (mid-march): The first jsr-tagged milestone will contain both old and new parsers. By default, the new parser will be activated, but anybody will be able to move back to the old JSR parser by activating a specific flag. It will be an interim release which allows our users to see what impact the new JSR groovy has.
  • jsr-2 (mid-april): The second jsr-tagged milestone will get rid of the standard parser and use only the new parser. We should have the new markup feature integrated by this release (but hopefully sooner!)
  • jsr-3 (mid-may): The new parser should reach a final state, and the binary distribution become the RI deliverable of the JSR.

Final release

  • groovy-final-1.0 Reference Implementation (to be defined)
  • TCK (to be defined)
  • GLS (to be defined)

Functionality Roadmap

For a high level overview of the scope of the JSR 1.0 and 2.0 processes, please see the Scope Overview

To have an overview of all the improvements, wishes, or bugs in our project tracker, please refer to JIRA:
JIRA issue tracker

Transition period

We will post notes in that section to ease the transition phase between both pre- and post-jsr parsers. Here is a summary of Migration From Classic to JSR syntax

  • No labels