You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@groovy.apache.org by Paul King <pa...@asert.com.au> on 2017/07/23 00:07:30 UTC
upcoming release(s)
Hi everyone,
We are planning to release 2.4.13, 2.5.0-beta-2 and the first alpha release
of 2.6.0 and/or 3.0.0 over the coming weeks. We already have a bunch of
fixes/features we are targeting for those releases but we are keen for any
feedback. If there is a particular release you are waiting for or
particular bugs/features, let us know and that can help us set priorities.
Some of us have the opportunity at the upcoming GR8Conf US for some more
in-depth discussions. And certainly, for those that can't make it to the
conference, don't let that stop you from submitting PRs! :-)
Cheers, Paul.
Re: upcoming release(s)
Posted by Paul King <pa...@asert.com.au>.
Okay, I'll have to look into it. That issue says resolved in 2.4.12 but the
CI build is pointing to 2.4.13-SNAPSHOT, so I'll have to investigate.
On Sat, Aug 5, 2017 at 5:28 PM, Paolo Di Tommaso <pa...@gmail.com>
wrote:
> Reading 2.4.13 it would be good to have 8157
> <https://issues.apache.org/jira/browse/GROOVY-8157> fixed in this
> release.
>
> Nextflow is currently reporting a bunch of errors caused by that issue.
> See here
> <http://ci.groovy-lang.org/project.html?projectId=JointBuilds_Nextflow&guest=1>
> .
>
>
> Cheers,
> Paolo
>
>
> On Sun, Jul 23, 2017 at 2:07 AM, Paul King <pa...@asert.com.au> wrote:
>
>>
>> Hi everyone,
>>
>> We are planning to release 2.4.13, 2.5.0-beta-2 and the first alpha
>> release of 2.6.0 and/or 3.0.0 over the coming weeks. We already have a
>> bunch of fixes/features we are targeting for those releases but we are keen
>> for any feedback. If there is a particular release you are waiting for or
>> particular bugs/features, let us know and that can help us set priorities.
>> Some of us have the opportunity at the upcoming GR8Conf US for some more
>> in-depth discussions. And certainly, for those that can't make it to the
>> conference, don't let that stop you from submitting PRs! :-)
>>
>> Cheers, Paul.
>>
>>
>
Re: upcoming release(s)
Posted by Paolo Di Tommaso <pa...@gmail.com>.
Reading 2.4.13 it would be good to have 8157
<https://issues.apache.org/jira/browse/GROOVY-8157> fixed in this release.
Nextflow is currently reporting a bunch of errors caused by that issue. See
here
<http://ci.groovy-lang.org/project.html?projectId=JointBuilds_Nextflow&guest=1>
.
Cheers,
Paolo
On Sun, Jul 23, 2017 at 2:07 AM, Paul King <pa...@asert.com.au> wrote:
>
> Hi everyone,
>
> We are planning to release 2.4.13, 2.5.0-beta-2 and the first alpha
> release of 2.6.0 and/or 3.0.0 over the coming weeks. We already have a
> bunch of fixes/features we are targeting for those releases but we are keen
> for any feedback. If there is a particular release you are waiting for or
> particular bugs/features, let us know and that can help us set priorities.
> Some of us have the opportunity at the upcoming GR8Conf US for some more
> in-depth discussions. And certainly, for those that can't make it to the
> conference, don't let that stop you from submitting PRs! :-)
>
> Cheers, Paul.
>
>
Re: upcoming release(s)
Posted by Ahm Avoby <al...@gmail.com>.
I usually just take what the newest Groovy release gives us - but now I am
curious: Where are the new features for 3.0 listed ? Groovy has no roadmap,
future outlook etc on the official webpage as far as I know ?
I am of course still very much interested in any feature that solves the
Minecraft-modding-obfuscation-problem. Waiting for @CompileStatic to become
more Java compatible, I have in the meantime autogenerated some
Groovy-to-Java-obfuscation-bridge-classes; this works reasonably well for
our own Entity and Block derived classes but of course cannot handle the
general case, so there we still get the MissingMethod/-Property exceptions.
Because of that we had to step back for some classes to use Java instead of
Groovy again :-(
Kind regards
Daniel Sun <re...@hotmail.com> schrieb am So., 23. Juli 2017, 13:55:
> Looking forward to 2.6.0 and 3.0.0, which contains the Parrot parser
> providing many new features :)
>
> p.s. use -Dgroovy.antlr4=true to enable the Parrot parser
>
> Cheers,
> Daniel.Sun
>
>
>
> --
> View this message in context:
> http://groovy.329449.n5.nabble.com/upcoming-release-s-tp5742269p5742275.html
> Sent from the Groovy Users mailing list archive at Nabble.com.
>
Re: upcoming release(s)
Posted by Russel Winder <ru...@winder.org.uk>.
On Sun, 2017-07-23 at 04:55 -0700, Daniel Sun wrote:
> Looking forward to 2.6.0 and 3.0.0, which contains the Parrot parser
> providing many new features :)
>
> p.s. use -Dgroovy.antlr4=true to enable the Parrot parser
>
Will the new parser not be the default in Groovy 3?
--
Russel.
=============================================================================
Dr Russel Winder t: +44 20 7585 2200 voip: sip:russel.winder@ekiga.net
41 Buckmaster Road m: +44 7770 465 077 xmpp: russel@winder.org.uk
London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder
Re: upcoming release(s)
Posted by Daniel Sun <re...@hotmail.com>.
Looking forward to 2.6.0 and 3.0.0, which contains the Parrot parser
providing many new features :)
p.s. use -Dgroovy.antlr4=true to enable the Parrot parser
Cheers,
Daniel.Sun
--
View this message in context: http://groovy.329449.n5.nabble.com/upcoming-release-s-tp5742269p5742275.html
Sent from the Groovy Users mailing list archive at Nabble.com.