Castellers

We are maintaining multiple GlassFish release trains to address different user needs, and I put together a summary to help you track them. First some terminology: • Sustaining - In sustaining mode; most changes will be addressing key bugs. • Active - Under active development. • Committed - Committed to happen, schedule may be flexible. • Scheduled - Release with a committed schedule. • Tentative - Release details still not firm.

GlassFish v1 (Sustaining)
• The first final release for this train was J1'06. Other public releases include GFv1 UR1 and GFv1 UR1p1. We are likely to do another public release as soon as we close on GFv2.
• Commercial support is currently available from Sun under the SJS AS 9.0 brand, with releases every 6-8 weeks or so.

GlassFish v2 (Active, Scheduled)
• Adds clustering, profiles, many performance improvements, etc. Published SPECj2004 AppServer numbers.
• Release is planned to go final in a few weeks, in mid-September.
• Commercial support from Sun under the SJS AS 9.1 brand name.

GlassFish v2 UR (Tentative)
• Every major release has an Update Release; it is part of the physics of releases :-)
• Commercial support under the tentative SJS AS 9.1 UR1 brand name.
• Currently pencilled for release at the beginning of 2008.

Sailfin (Active, Committed)
• Adds increased scalability and reliability constraints, as well as SIP Servlet and additional Communication features.
• Tentatively scheduled for mid 2008.

GlassFish v2.next (Active, Tentative)
• GF v2 release based on Sailfin; should include all the improvements in the base AppServer needed to deliver Sailfin.
• Exact packaging relationship to Sailfin still undecided, it is too early to understand the impact of different trade-offs.

GlassFish v3 (Active, Tentative)
• The main feature is a modular architecture based on HK2.
• Services will be added to this train incrementally.
• A key challenge is to maintain usability in the administration while making it modular.
• We may define a web tier/ web services / scripting milestone with limited adminitrative GUI.
• Final release of full AppServer may be aligned with Java EE 6.

Note: All these releases are public open source code. And they will all be supported by Sun via enterprise-grade distributions.