Hi everyone,

I haven't had anyone request the need for an RC2. So, I'll move forward
with the 5.0.0 release.

There are no significant changes since RC1 to the core classes - mostly
just ongoing groovysh repl changes and I suspect it will be an
evolving area as upstream PRs are merged (or not) and we can remove some
existing workarounds (or make them permanent).

If anyone notices problems that are as yet undetected, I can do a
re-roll of the release if needed. We often find folks don't actually test
the new version until we go GA. We can also easily do some quick 5.0.1,
5.0.2, ... releases if the need arises as folks start using the new version
in larger numbers.

Cheers, Paul.


On Fri, Aug 15, 2025 at 7:47 AM Paul King <pa...@asert.com.au> wrote:

>
> Hi folks,
>
> I think we are (almost) ready for a Groovy 5 release. We only have a
> handful of changes since RC1. Mostly the changes are to do with groovysh
> which could certainly do with some more testing. If folks are happy to test
> groovysh by building on master (installGroovy task), I can wait until folks
> have found time to do that. Alternatively, if folks would like an RC2
> release to test I can go ahead with such a release first.
>
> There are still things we are working on:
> * OSGi work to support two flavours of usage that our users seem to have
> * looking at a serialization issue which might make an edge case more
> robust
> * some performance issues
> * some upstream JLine fixes we have submitted
>
> If anyone has time to work on any of those, let me know and I can go into
> more details and point you to issues. We'll obviously include any
> advancements on those topics if we make progress.
>
> But otherwise, I think we can go ahead with a GA release and fix the above
> things in the normal way with our point releases. Folks not impacted by the
> above can start using Groovy 5 in the meantime. Most of our users won't be
> affected by those issues and they could also give us further feedback in
> parallel.
>
> Thoughts?
>
> Cheers,
> Paul.
>
>

Reply via email to