GlassFish Development Branches

And then there were three ...

GlassFish V2 is done. So, what's next? Well, there is a lot of information out there about GlassFish V3 but that is not the only release that the GlassFish team is working on. There are at least two more releases planned, GlassFish V2 UR1 (an update release) and GlassFish V2.next (a minor release). Some information on these releases is already available on blogs and GlassFish wiki. The best place to start is Eduardo's blog entry on GlassFish roadmap. The draft plan for V2 UR1 is available on GlassFish Wiki. As Eduardo mentioned, the V2.next release is still being defined. However, it is very likely that the release will be called V2.1 and therefore I will take the liberty of using that name throughout this blog. The primary driver for this release is requirements for sailfin project. The GlassFish wiki is again the best way to keep up to date with the planning for V2.1 release.

The following image shows the many development branches for GlassFish. The V1 release is not shown here because that would make this picture even more complex.

A picture is worth a thousand words, so I will not explain this picture :-) I do realize that there will be many questions as you try to understand it. Please leave a comment with your question and I will try to address it. If the volume of comments in too high, I will write another blog to explain it better.

As far as GlassFish V3 is concerned, please continue to watch the V3 planning wiki where the team will be adding more information over next several weeks. If you have some time, I recommend viewing Kohsuke's presentation on the new build system. This will be a good time to start getting familiar with maven 2.0. Jerome is working on creating the initial version of POM files for several modules and once they are ready, the next step will be for the module leads to start planning transition of their modules to maven 2.0 and the new build system.

Posted at 01:13AM Sep 24, 2007 by kumara in Sun  |  Comments[2]