You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@groovy.apache.org by Christopher Smith <ch...@gmail.com> on 2022/07/29 22:12:19 UTC
Request for releases
I am aware that we've just had a release batch, but I would like to request
another release to include Eric's graciously quick fix for GROOVY-10711.
This bug resulted in the static compiler's silently failing to use
`asBoolean()` methods defined directly on classes, which can result in data
corruption.
Re: Request for releases
Posted by Paul King <pa...@asert.com.au>.
Yes, I'll look at expediting a release but it will likely be a few
days away since there are a couple of other bug fixes we'd like
included. I'll add some more info into the Jira issue as soon as I
can.
On Sat, Jul 30, 2022 at 8:33 AM Christopher Smith <ch...@gmail.com> wrote:
>
> Given the potential severity of this bug (i.e., conditional checks will compile fine but use the wrong logic), I would suggest a release now, but I of course am not the one who has to do the paperwork. ;-) I'm aware of this problem, but most Groovy users wouldn't be, and it affects at least 3.x and 4.x.
>
> On Fri, Jul 29, 2022 at 5:27 PM Paul King <pa...@asert.com.au> wrote:
>>
>> I was planning to perhaps do a 4.0.5 release not too far away (as in
>> maybe 1-2 weeks time). Were you wanting faster than that or also a
>> 3.0.13?
>>
>> On Sat, Jul 30, 2022 at 8:12 AM Christopher Smith
>> <ch...@gmail.com> wrote:
>> >
>> > I am aware that we've just had a release batch, but I would like to request another release to include Eric's graciously quick fix for GROOVY-10711. This bug resulted in the static compiler's silently failing to use `asBoolean()` methods defined directly on classes, which can result in data corruption.
>
>
>
> --
> Christopher Smith
Re: Request for releases
Posted by Christopher Smith <ch...@gmail.com>.
Given the potential severity of this bug (i.e., conditional checks will
compile fine but use the wrong logic), I would suggest a release now, but I
of course am not the one who has to do the paperwork. ;-) I'm aware of this
problem, but most Groovy users wouldn't be, and it affects at least 3.x and
4.x.
On Fri, Jul 29, 2022 at 5:27 PM Paul King <pa...@asert.com.au> wrote:
> I was planning to perhaps do a 4.0.5 release not too far away (as in
> maybe 1-2 weeks time). Were you wanting faster than that or also a
> 3.0.13?
>
> On Sat, Jul 30, 2022 at 8:12 AM Christopher Smith
> <ch...@gmail.com> wrote:
> >
> > I am aware that we've just had a release batch, but I would like to
> request another release to include Eric's graciously quick fix for
> GROOVY-10711. This bug resulted in the static compiler's silently failing
> to use `asBoolean()` methods defined directly on classes, which can result
> in data corruption.
>
--
Christopher Smith
Re: Request for releases
Posted by Paul King <pa...@asert.com.au>.
I was planning to perhaps do a 4.0.5 release not too far away (as in
maybe 1-2 weeks time). Were you wanting faster than that or also a
3.0.13?
On Sat, Jul 30, 2022 at 8:12 AM Christopher Smith
<ch...@gmail.com> wrote:
>
> I am aware that we've just had a release batch, but I would like to request another release to include Eric's graciously quick fix for GROOVY-10711. This bug resulted in the static compiler's silently failing to use `asBoolean()` methods defined directly on classes, which can result in data corruption.