Skip to main content

Announcing an upcoming GlassFish (micro) release

4 replies [Last post]
jclingan
Offline
Joined: 2003-06-12

Upon feedback from the community on some of the issues in GlassFish 3.1.2 (see [1], [2], [3]), the GlassFish team has decided to do a new micro release to address them. This is an exception to the normal release process but we believe that it is important to address the issues to help our community of users. We are working on the details of timeline and other fixes (if any) that will be included in the release and will share more information soon.

[1] http://netbeans.org/bugzilla/show_bug.cgi?id=211962
[2] http://java.net/jira/browse/JAX_WS-1059
[3] http://java.net/jira/browse/GLASSFISH-18446

Thanks!

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
jsl123
Offline
Joined: 2006-07-20

On 05/07/2012 16:44, John Clingan wrote:
> Upon feedback from the community on some of the issues in GlassFish
> 3.1.2 (see [1], [2], [3]), the GlassFish team has decided to do a new
> micro release to address them. This is an exception to the normal
> release process but we believe that it is important to address the
> issues to help our community of users. We are working on the details
> of timeline and other fixes (if any) that will be included in the
> release and will share more information soon.
>
> [1] http://netbeans.org/bugzilla/show_bug.cgi?id=211962
> [2] http://java.net/jira/browse/JAX_WS-1059
> [3] http://java.net/jira/browse/GLASSFISH-18446
>
> Thanks!
Firstly, thanks that is a welcome update for a couple of big issues.
However I was wondering what has happened to using the update tool to
patch glassfish out of a release cycle. The recent versions don't seem
to have had any updates, whereas I seem to remember out of cycle updates
for older versions of glassfish using the update tool...

Thanks

John

jclingan
Offline
Joined: 2003-06-12

This time, replying to the list ....

John, as a Product Manager on GlassFish Server since 2007, I don't
recall us releasing module updates on core runtime GlassFish Server
modules. That being said, this is something that we have been
discussing for a while and something that we would generally like to do
as a means of improving the developer experience.

The update center offers the ability to deliver incremental module
updates. The problem is that releasing individual module updates does
not match our long-standing development, sustaining, and QA processes.
For this reason, we are being a bit cautious about how we push out
updates. It is why GlassFish 3.1.2.2 is more the exception than the
rule.

Additional feedback is welcome.

Korbinian Bachl

Please include http://java.net/jira/browse/GLASSFISH-18705 in it as its a
very bad one affecting many users;
Also http://java.net/jira/browse/GLASSFISH-18444 is important as it
suddenly changed file-upload behaviour in a MINOR release, thus breaking
lots of applications out there....

Regards

2012/7/5 John Clingan

> Upon feedback from the community on some of the issues in GlassFish 3.1.2
> (see [1], [2], [3]), the GlassFish team has decided to do a new micro
> release to address them. This is an exception to the normal release process
> but we believe that it is important to address the issues to help our
> community of users. We are working on the details of timeline and other
> fixes (if any) that will be included in the release and will share more
> information soon.
>
> [1] http://netbeans.org/bugzilla/show_bug.cgi?id=211962
> [2] http://java.net/jira/browse/JAX_WS-1059
> [3] http://java.net/jira/browse/GLASSFISH-18446
>
> Thanks!
>

jclingan
Offline
Joined: 2003-06-12

Korbinian, thanks for the feedback.

For the former bug (a commercial-oriented issue), the generaly
recommendation is to open up a bug report as a commercial customer and
it will get fixed in a patch release or wait until a release of
GlassFish release is delivered. That being said, stay tuned on this
one. We'll look into it.

As for the latter, sincere apologies on the backwards compatibility
issue. Looks like a fix was pushed out.