Re: Upcoming releases: 2.4.18/2.5.9/final 3.0 RC

[Daniel.Sun]

Hi Paul,

I suggest the following PRs could be included in final 3.0 RC.

1)  PR#1135[1] for GROOVY-8298 is ready to merge
2)  PR#1137[2] for GROOVY-8296 LGTM

Cheers,
Daniel.Sun
[1] https://github.com/apache/groovy/pull/1135
[2] https://github.com/apache/groovy/pull/1137



-
Apache Groovy committer & PMC member 
Blog: http://blog.sunlan.me 
Twitter: @daniel_sun 

--
Sent from: http://groovy.329449.n5.nabble.com/Groovy-Dev-f372993.html

Re: Upcoming releases

[Paul King]

I merged most of Eric's listed issues. Any last call before I proceed with
RC-2 for Groovy 3?
I'll progress 2.5.9 and the other potential branches after this one is out.

Cheers, Paul.

On Mon, Nov 11, 2019 at 4:21 PM Paul King  wrote:

>
> We plan to do a RC-2 release shortly (possibly next week) and it's
> probably also time for releases on other branches. The 2.5 branch has
> numerous fixes. The 2.4 branch is nominally unsupported but we have been
> asked to do another release to get some key fixes onto that branch. And an
> alpha of 4.0 is also on the cards.
>
> Please let us know if there are specific fixes you want for any of those
> releases.
>
> Cheers, Paul.
>
>

Re: Upcoming releases

[Remi Forax]

ASM is backward compatible since ASM 4.

Rémi

- Mail original -
> De: "Jochen Theodorou" 
> À: "dev" 
> Envoyé: Mardi 12 Novembre 2019 23:15:40
> Objet: Re: Upcoming releases

> On 12.11.19 08:14, Cédric Champeau wrote:
>> Just saying that using external ASM is an option now. Back then we had
>> to repackage because ASM wasn't backwards compatible so triggered all
>> sorts of problems when another library used it with a different version.
>> This is not the case now since you always pass in the ASM version in the
>> constructor now, so ASM knows what visitor to use.
> 
> You remember the ASM version this was? Was it ASM 5?
> 
> bye blackdrag

Re: Upcoming releases

[Jochen Theodorou]

On 12.11.19 08:14, Cédric Champeau wrote:

Just saying that using external ASM is an option now. Back then we had
to repackage because ASM wasn't backwards compatible so triggered all
sorts of problems when another library used it with a different version.
This is not the case now since you always pass in the ASM version in the
constructor now, so ASM knows what visitor to use.


You remember the ASM version this was? Was it ASM 5?

bye blackdrag

Re: Upcoming releases

[Cédric Champeau]

Just saying that using external ASM is an option now. Back then we had to
repackage because ASM wasn't backwards compatible so triggered all sorts of
problems when another library used it with a different version.
This is not the case now since you always pass in the ASM version in the
constructor now, so ASM knows what visitor to use.

Le mar. 12 nov. 2019 à 03:56, Daniel.Sun  a écrit :

> Here is the PR "GROOVY-9262: Bump asm to 7.2":
> https://github.com/apache/groovy/pull/1081
>
>
> Cheers,
> Daniel.Sun
>
>
>
> -
> Apache Groovy committer & PMC member
> Blog: http://blog.sunlan.me
> Twitter: @daniel_sun
>
> --
> Sent from: http://groovy.329449.n5.nabble.com/Groovy-Dev-f372993.html
>

Re: Upcoming releases

[Daniel.Sun]

Here is the PR "GROOVY-9262: Bump asm to 7.2": 
https://github.com/apache/groovy/pull/1081


Cheers,
Daniel.Sun



-
Apache Groovy committer & PMC member 
Blog: http://blog.sunlan.me 
Twitter: @daniel_sun 

--
Sent from: http://groovy.329449.n5.nabble.com/Groovy-Dev-f372993.html

Re: Upcoming releases

[Daniel.Sun]

Hi Jochen,

> 2.5 is on ASM 7.1, newest version is 7.2? I think that kind of update is
> still a possibility. Paul? Daniel? 

 Yep :-)

> Considering GROOVY-9271 I wonder
> actually we did not go to 7.2 right away for 2.4...

Upgrading to 7.X from 6.X is a big change. Frankly I am not sure if
breaking changes will be introduced.

Cheers,
Daniel.Sun



-
Apache Groovy committer & PMC member 
Blog: http://blog.sunlan.me 
Twitter: @daniel_sun 

--
Sent from: http://groovy.329449.n5.nabble.com/Groovy-Dev-f372993.html

Re: Upcoming releases

[Jochen Theodorou]

On 11.11.19 12:35, Andres Almiray wrote:

Hello there,

I spoke with Rémi Forax at Devoxx justa  few days ago regarding a
message sent to the Openjdk dev list related to Groovy/Gradle/ASM. Long
story short the toolchain is not updated because Groovy does not publish
a release with the latest ASM, which makes really hard to build projects
with latest OpenJDK early access builds because Gradle croaks.

A couple of ideas:
- push a Groovy release where the only change is an upgrade to latest
ASM release. In this way the Gradle team can test if any regressions
occur _only_ by ASM and not because we added something extra.
- stop shading ASM and use it as a regular dependency. Apparently we
used to shade ASM for valid reasons in the past, but now that we publish
Groovy as a BOM we may rely on regular dependencies.

I'm aware that any of these two changes do not constitute a change one
usually push during an RC cycle.


2.5 is on ASM 7.1, newest version is 7.2? I think that kind of update is
still a possibility. Paul? Daniel? Considering GROOVY-9271 I wonder
actually we did not go to 7.2 right away for 2.4...

The reason we shade Groovy is because many libraries use ASM and not all
version of ASM are compatible with each other. With the module system I
actually see more reasons to shade than less.

We could think to offer a version that uses the shaded ASM coming with
the JDK itself... though... not as easy with the module system?

Not wanting to push away responsibility, but there would also be the
possibility to replace the ASM lib within Groovy by the build process
Gradle uses.


bye blackdrag

Re: Upcoming releases

[Paul King]

Many of those won't merge cleanly - I had tried a few already but I'll see
what can be done.

On Tue, Nov 12, 2019 at 1:35 AM Milles, Eric (TR Tech, Content & Ops) <
eric.mil...@thomsonreuters.com> wrote:

> I know this seems like a lot to ask for 2.5.9, but I scanned the commits
> in master and there are individual commits tagged with the following bug
> fixes:
>
> GROOVY-7722
> GROOVY-8372
> GROOVY-8305
> GROOVY-8507, GROOVY-9301
> GROOVY-8457
> GROOVY-9257
> GROOVY-9195
> GROOVY-9127
> GROOVY-9294
> GROOVY-7996
> GROOVY-6996
> GROOVY-9266
> GROOVY-9244
> GROOVY-9270
> GROOVY-9240
> GROOVY-9229, GROOVY-9233
>
> If any particular commit does not merge cleanly, I could help backport or
> evaluate if it should be excluded.
>
> --
> *From:* Paul King 
> *Sent:* Monday, November 11, 2019 12:21 AM
> *To:* Groovy_Developers 
> *Subject:* Upcoming releases
>
>
> We plan to do a RC-2 release shortly (possibly next week) and it's
> probably also time for releases on other branches. The 2.5 branch has
> numerous fixes. The 2.4 branch is nominally unsupported but we have been
> asked to do another release to get some key fixes onto that branch. And an
> alpha of 4.0 is also on the cards.
>
> Please let us know if there are specific fixes you want for any of those
> releases.
>
> Cheers, Paul.
>
>

Re: Upcoming releases

[Andres Almiray]

Hello there,

I spoke with Rémi Forax at Devoxx justa  few days ago regarding a message
sent to the Openjdk dev list related to Groovy/Gradle/ASM. Long story short
the toolchain is not updated because Groovy does not publish a release with
the latest ASM, which makes really hard to build projects with latest
OpenJDK early access builds because Gradle croaks.

A couple of ideas:
- push a Groovy release where the only change is an upgrade to latest ASM
release. In this way the Gradle team can test if any regressions occur
_only_ by ASM and not because we added something extra.
- stop shading ASM and use it as a regular dependency. Apparently we used
to shade ASM for valid reasons in the past, but now that we publish Groovy
as a BOM we may rely on regular dependencies.

I'm aware that any of these two changes do not constitute a change one
usually push during an RC cycle.

Cheers,
Andres

---
Java Champion; Groovy Enthusiast
http://andresalmiray.com
http://www.linkedin.com/in/aalmiray
--
What goes up, must come down. Ask any system administrator.
There are 10 types of people in the world: Those who understand binary, and
those who don't.
To understand recursion, we must first understand recursion.


On Mon, Nov 11, 2019 at 7:22 AM Paul King  wrote:

>
> We plan to do a RC-2 release shortly (possibly next week) and it's
> probably also time for releases on other branches. The 2.5 branch has
> numerous fixes. The 2.4 branch is nominally unsupported but we have been
> asked to do another release to get some key fixes onto that branch. And an
> alpha of 4.0 is also on the cards.
>
> Please let us know if there are specific fixes you want for any of those
> releases.
>
> Cheers, Paul.
>
>

Re: Upcoming releases

[Paolo Di Tommaso]

The current 2.5 snapshot is producing an error in the nextflow joint build.
It seems due to a false positive variable uninitialised check:


[03:16:26][:compileGroovy] Note: /var/teamcity/buildagent-jdk8/
work/fcd731bd66de729d/src/main/groovy/nextflow/sort/BigSort.java uses
unchecked or unsafe operations.
[03:16:26][:compileGroovy] Note: Recompile with -Xlint:unchecked for
details.
[03:16:30][:compileGroovy] startup failed:
[03:16:30][:compileGroovy] /var/teamcity/buildagent-jdk8/
work/fcd731bd66de729d/src/main/groovy/nextflow/processor/TaskProcessor.groovy:
941: The variable [str] may be uninitialized
[03:16:30][:compileGroovy] . At [941:24]  @ line 941, column 24.
[03:16:30][:compileGroovy]exitCode = str.isInteger() ?
str.toInteger() : null
[03:16:30][:compileGroovy]   ^
[03:16:30][:compileGroovy]
[03:16:30][:compileGroovy] 1 error
[03:16:30][:compileGroovy]


See more here
.
The source is here
.
Let me know if you want to open an issue for this.


Cheers,
Paolo


On Tue, Feb 6, 2018 at 8:19 AM, Paul King  wrote:

>
> I am planning to prepare a 2.5.0-beta-3 release towards the end of this
> week and 2.4.14 not long after. Now's a good time to let us know if there
> is something critical you need for those releases.
>
> I am expecting 2.5.0-beta-3 to be the last beta for 2.5.0 and while there
> are a couple of things we are still planning to finish for 2.5.0, I am
> expecting the next release to kick off the RC release(s), so a final
> release shouldn't be too far away!
>
> Thanks, Paul.
>
>

Re: Upcoming releases

[Daniel Sun]

You can ping Cédric  ;-)



--
Sent from: http://groovy.329449.n5.nabble.com/Groovy-Dev-f372993.html

RE: Upcoming releases

[Daniel Sun]

Hi Eric,

 No worries ;-)   As you can see, new language features for 3.0 are
almost frozen. The reason why I try to release 2.6 and 3.0 alpha versions is
to let groovy users try and give us feedback in time. Anyway, I will take
into account your worries  and release 2.6 and 3.0 after 2.4 and 2.5
released.

BTW, the eclipse plugin for Groovy is awesome, thanks for your hard work
:-)

Cheers,
Daniel.Sun



--
Sent from: http://groovy.329449.n5.nabble.com/Groovy-Dev-f372993.html

Re: Upcoming releases

[Shil Sinha]

If anyone involved in android support is reading this, could they please
review https://github.com/apache/groovy/pull/648 ? I'd like to get that in
2.5.

On Tue, Feb 6, 2018 at 10:25 AM, <eric.mil...@thomsonreuters.com> wrote:

> Daniel,
> Could you please wait?  Each time Paul has announced 2.4 and 2.5 releases
> forthcoming, you announce 2.6 and 3.0 minutes later.  Then you end up
> forcing out 2.6 and 3.0 before 2.4 and 2.5.  This strains the intake
> pipelines of downstream projects like IDE support, etc.
>
> -Original Message-
> From: Daniel Sun [mailto:realblue...@hotmail.com]
> Sent: Tuesday, February 06, 2018 4:38 AM
> To: d...@groovy.incubator.apache.org
> Subject: Re: Upcoming releases
>
> That's great.
>
> I plan to release 2.6-alpha-3 and 3.0-alpha-2 when the PR(
> https://urldefense.proofpoint.com/v2/url?u=https-
> 3A__github.com_apache_groovy_pull_654=DwICAg=4ZIZThykDLcoWk-GVjSLmy8-
> 1Cr1I4FWIvbLFebwKgY=tPJuIuL_GkTEazjQW7vvl7mNWVGXn3yJD5LGBH
> YYHww=ssQVk8MzUlEqENextdc-oXwd4p512ZCoPo5L1rCvNTI=
> Zva9_D9ZBNuGZxlFEFVCYvHybCOd4-XvNIJF5MnagKw= ) is reviewed and merged.
>
> Cheers,
> Daniel.Sun
>
>
>
>
> --
> Sent from: https://urldefense.proofpoint.com/v2/url?u=http-3A__groovy.
> 329449.n5.nabble.com_Groovy-2DDev-2Df372993.html=DwICAg&
> c=4ZIZThykDLcoWk-GVjSLmy8-1Cr1I4FWIvbLFebwKgY=tPJuIuL_
> GkTEazjQW7vvl7mNWVGXn3yJD5LGBHYYHww=ssQVk8MzUlEqENextdc-
> oXwd4p512ZCoPo5L1rCvNTI=VAcvRrEcFIkiJVJ5bPj6Ow9J5kvkaXa0AHFnnux77i4=
>

RE: Upcoming releases

[eric.milles]

Daniel,
Could you please wait?  Each time Paul has announced 2.4 and 2.5 releases 
forthcoming, you announce 2.6 and 3.0 minutes later.  Then you end up forcing 
out 2.6 and 3.0 before 2.4 and 2.5.  This strains the intake pipelines of 
downstream projects like IDE support, etc.

-Original Message-
From: Daniel Sun [mailto:realblue...@hotmail.com] 
Sent: Tuesday, February 06, 2018 4:38 AM
To: d...@groovy.incubator.apache.org
Subject: Re: Upcoming releases

That's great.

I plan to release 2.6-alpha-3 and 3.0-alpha-2 when the 
PR(https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_apache_groovy_pull_654=DwICAg=4ZIZThykDLcoWk-GVjSLmy8-1Cr1I4FWIvbLFebwKgY=tPJuIuL_GkTEazjQW7vvl7mNWVGXn3yJD5LGBHYYHww=ssQVk8MzUlEqENextdc-oXwd4p512ZCoPo5L1rCvNTI=Zva9_D9ZBNuGZxlFEFVCYvHybCOd4-XvNIJF5MnagKw=
 ) is reviewed and merged.

Cheers,
Daniel.Sun




--
Sent from: 
https://urldefense.proofpoint.com/v2/url?u=http-3A__groovy.329449.n5.nabble.com_Groovy-2DDev-2Df372993.html=DwICAg=4ZIZThykDLcoWk-GVjSLmy8-1Cr1I4FWIvbLFebwKgY=tPJuIuL_GkTEazjQW7vvl7mNWVGXn3yJD5LGBHYYHww=ssQVk8MzUlEqENextdc-oXwd4p512ZCoPo5L1rCvNTI=VAcvRrEcFIkiJVJ5bPj6Ow9J5kvkaXa0AHFnnux77i4=
 

Re: Upcoming releases

[Daniel Sun]

That's great.

I plan to release 2.6-alpha-3 and 3.0-alpha-2 when the
PR(https://github.com/apache/groovy/pull/654) is reviewed and merged.

Cheers,
Daniel.Sun




--
Sent from: http://groovy.329449.n5.nabble.com/Groovy-Dev-f372993.html

Re: Upcoming releases

[Paolo Di Tommaso]

I renew my plea for this PR

https://github.com/apache/groovy/pull/566


Cheers,
Paolo




On Tue, Feb 6, 2018 at 9:11 AM, Mario Garcia  wrote:

> That's good News :)
>
> 2018-02-06 8:19 GMT+01:00 Paul King :
>
>>
>> I am planning to prepare a 2.5.0-beta-3 release towards the end of this
>> week and 2.4.14 not long after. Now's a good time to let us know if there
>> is something critical you need for those releases.
>>
>> I am expecting 2.5.0-beta-3 to be the last beta for 2.5.0 and while there
>> are a couple of things we are still planning to finish for 2.5.0, I am
>> expecting the next release to kick off the RC release(s), so a final
>> release shouldn't be too far away!
>>
>> Thanks, Paul.
>>
>>
>

Re: Upcoming releases

[Mario Garcia]

That's good News :)

2018-02-06 8:19 GMT+01:00 Paul King :

>
> I am planning to prepare a 2.5.0-beta-3 release towards the end of this
> week and 2.4.14 not long after. Now's a good time to let us know if there
> is something critical you need for those releases.
>
> I am expecting 2.5.0-beta-3 to be the last beta for 2.5.0 and while there
> are a couple of things we are still planning to finish for 2.5.0, I am
> expecting the next release to kick off the RC release(s), so a final
> release shouldn't be too far away!
>
> Thanks, Paul.
>
>

Re: upcoming releases

[Daniel.Sun]

Hi Cédric,

   Groovy 3.0.0 alpha can help groovy developers try the new parser
easily, which is enabled by default. In addition, we can get more feedback
earlier. So if no -1 on releasing 3.0.0 alpha, I'll try to release later.

Cheers,
Daniel.Sun



--
Sent from: http://groovy.329449.n5.nabble.com/Groovy-Dev-f372993.html

Re: upcoming releases

[Paul King]

Nor a 2.5! :-) My focus right now is progressing 2.5 out the door but that
will happen after G3 Summit. I have some final variable analysis tweaks
ready to add which should make 2.5 close to feature complete but there are
some Spock hacks that need further testing. (Spock doesn't currently set
the accessed variable when transforming local variable definitions and that
breaks FVA and possibly other typing checks). We possibly need to have
better recommended conventions around generated code in xforms. We
currently do FVA checking and possibly type checking on internal Spock
local variables for instance, e.g. $spock_errorCollector. We could skip
synthetic or @Generated variables (or ones with internal looking names -
but that can be problematic) for instance.

I am +0 on a 3 alpha. I think we have quite a few things to work through
before any 2.6/3 candidate will be close to final but if people want to
play with an early alpha I see no harm.

Cheers, Paul.


On Fri, Nov 24, 2017 at 7:26 PM, Cédric Champeau 
wrote:

> I'm not sure it makes sense to release a 3.0.0 alpha when we don't even
> have a 2.6 out.
>
> 2017-11-24 10:22 GMT+01:00 Daniel.Sun :
>
>> Hi Paul,
>>
>>   As Groovy 2.4.13 has been released, I plan to release Groovy
>> 3.0.0-alpha-1 later.
>>
>> Cheers,
>> Daniel.Sun
>>
>>
>>
>> --
>> Sent from: http://groovy.329449.n5.nabble.com/Groovy-Dev-f372993.html
>>
>
>

Re: upcoming releases

[Cédric Champeau]

I'm not sure it makes sense to release a 3.0.0 alpha when we don't even
have a 2.6 out.

2017-11-24 10:22 GMT+01:00 Daniel.Sun :

> Hi Paul,
>
>   As Groovy 2.4.13 has been released, I plan to release Groovy
> 3.0.0-alpha-1 later.
>
> Cheers,
> Daniel.Sun
>
>
>
> --
> Sent from: http://groovy.329449.n5.nabble.com/Groovy-Dev-f372993.html
>

Re: upcoming releases

[Daniel.Sun]

Hi Paul,

  As Groovy 2.4.13 has been released, I plan to release Groovy
3.0.0-alpha-1 later.

Cheers,
Daniel.Sun



--
Sent from: http://groovy.329449.n5.nabble.com/Groovy-Dev-f372993.html

RE: upcoming releases

[eric.milles]

Are we really ready to have 3 unfinished versions making their way through 
alpha/beta?  I haven't even had time to look into 2.6 yet.

Re: upcoming releases

[Daniel Sun]

OK. I'll release 3.0.0-alpha-1 after you fix the two known issues ;-)

Cheers,
Daniel.Sun

On 2017-11-16 16:41, Paul King  wrote: 
> Sounds good but I'd wait until the two known issues with 2.4.13 are fixed,
> otherwise you'll need to release note those problems as known issues. I'm
> working on one now and plan to look at the other next.
> 
> Cheers, Paul.
> 
> On Thu, Nov 16, 2017 at 11:37 AM, Daniel.Sun  wrote:
> 
> > Hi Paul,
> >
> >   Apart from 2.6.0-alpha-2, I plan to release 3.0.0-alpha-1 :-)
> >
> >
> > Cheers,
> > Daniel.Sun
> >
> >
> >
> > --
> > Sent from: http://groovy.329449.n5.nabble.com/Groovy-Dev-f372993.html
> >
> 

Re: upcoming releases

[Paul King]

Sounds good but I'd wait until the two known issues with 2.4.13 are fixed,
otherwise you'll need to release note those problems as known issues. I'm
working on one now and plan to look at the other next.

Cheers, Paul.

On Thu, Nov 16, 2017 at 11:37 AM, Daniel.Sun  wrote:

> Hi Paul,
>
>   Apart from 2.6.0-alpha-2, I plan to release 3.0.0-alpha-1 :-)
>
>
> Cheers,
> Daniel.Sun
>
>
>
> --
> Sent from: http://groovy.329449.n5.nabble.com/Groovy-Dev-f372993.html
>

Re: upcoming releases

[Daniel.Sun]

Hi Paul,

  Apart from 2.6.0-alpha-2, I plan to release 3.0.0-alpha-1 :-)


Cheers,
Daniel.Sun



--
Sent from: http://groovy.329449.n5.nabble.com/Groovy-Dev-f372993.html

Re: upcoming releases

[Paolo Di Tommaso]

Eventually this PR in 2.5-beta-3

https://github.com/apache/groovy/pull/566


Cheers,
Paolo


On Mon, Nov 6, 2017 at 7:00 PM,  wrote:

> And https://issues.apache.org/jira/browse/GROOVY-8289 is causing us a lot
> of pain in the debugger and appears to have a simple solution.
>

Re: Upcoming releases

[Paul King]

Okay, it took a bit longer than I expected but I plan to merge in PR#610
and PR#611 tomorrow and then start phase 1 of the 2.5.0-beta-2 release. Not
all the fixes people asked for are in their yet. They will need to wait
until next time.

Cheers, Paul.


On Wed, Sep 13, 2017 at 4:18 AM, Dominik Przybysz 
wrote:

> Hi,
> is there any chance that these two issues will be resolved in next groovy
> version?
>
> https://issues.apache.org/jira/browse/GROOVY-7981
> https://issues.apache.org/jira/browse/GROOVY-8281
>
> The second one is the most interesting to me.
>
> 2017-09-12 11:17 GMT+02:00 Daniel Sun :
>
>> +1
>>
>> In addition, it would be good to release 2.6.0-alpha-2/2.6.0-beta-1
>> within a
>> month or two :)
>>
>> Cheers,
>> Daniel.Sun
>>
>>
>>
>> --
>> Sent from: http://groovy.329449.n5.nabble.com/Groovy-Dev-f372993.html
>>
>
>
>
> --
> Pozdrawiam / Regards,
> Dominik Przybysz
>

Re: Upcoming releases

[Dominik Przybysz]

Hi,
is there any chance that these two issues will be resolved in next groovy
version?

https://issues.apache.org/jira/browse/GROOVY-7981
https://issues.apache.org/jira/browse/GROOVY-8281

The second one is the most interesting to me.

2017-09-12 11:17 GMT+02:00 Daniel Sun :

> +1
>
> In addition, it would be good to release 2.6.0-alpha-2/2.6.0-beta-1 within
> a
> month or two :)
>
> Cheers,
> Daniel.Sun
>
>
>
> --
> Sent from: http://groovy.329449.n5.nabble.com/Groovy-Dev-f372993.html
>



-- 
Pozdrawiam / Regards,
Dominik Przybysz

Re: Upcoming releases

[Daniel Sun]

+1

In addition, it would be good to release 2.6.0-alpha-2/2.6.0-beta-1 within a
month or two :)

Cheers,
Daniel.Sun



--
Sent from: http://groovy.329449.n5.nabble.com/Groovy-Dev-f372993.html

Re: Upcoming releases

[Paolo Di Tommaso]

If possible it would be nice to include GROOVY-8220
 and eventually this PR
.


Thanks,
Paolo


On Tue, Sep 12, 2017 at 9:33 AM, Guillaume Laforge 
wrote:

> +1!
>
> On Tue, Sep 12, 2017 at 9:27 AM, Paul King  wrote:
>
>>
>> Hi,
>>
>> I was planning to release 2.5.0-beta-2 probably first thing next week.
>> If you have any upcoming changes that you want in the release, please
>> get them in now or let me know if that time frame causes a problem.
>>
>> It will depend on whether we get much feedback on the beta but I would
>> anticipate moving towards the first RC release in the next month or two.
>> It would be good to get that release out the door so we can increase
>> focus on 2.6/3! :-)
>>
>> Cheers, Paul.
>>
>>
>
>
> --
> Guillaume Laforge
> Apache Groovy committer & PMC Vice-President
> Developer Advocate @ Google Cloud Platform
>
> Blog: http://glaforge.appspot.com/
> Social: @glaforge  / Google+
> 
>

Re: upcoming releases

[Paul King]

Just a slight deviation to below. The version number on master has
temporarily been set to 2.9.98-SNAPSHOT pending Spock support of
Groovy 3+ version numbers.

Cheers, Paul.

On Wed, Mar 15, 2017 at 10:17 AM, Paul King  wrote:
> I have created the 2_5_X branch. I have made master 3.0.0(-SNAPSHOT)
> for now. This doesn't stop us having a 2.6 stream if we need it. Which
> I suspect we do but will cover that in another email.
>
> Just a reminder that for now any bugs fixes might need to be
> cherry-picked unto both the 2_5_X and 2_4_X branches. I will create
> additional CI jobs on teamcity over the coming week.
>
> Cheers, Paul.
>
>
> On Fri, Mar 10, 2017 at 12:10 AM, John Wagenleitner
>  wrote:
>> On Tue, Mar 7, 2017 at 1:40 PM, Paul King  wrote:
>>>
>>> Hi,
>>>
>>> I am planning to merge PR#508 and start the release process for 2.4.10
>>> over the next few days. This contains an important bug fix that
>>> affects downstream projects such as Grails. Any other fixes people
>>> want in that release?
>>>
>>> Soon after that is released I am planning to create a 2_5_X branch and
>>> begin preparation of a 2.5.0 release. If our review/rework of macros
>>> is complete by then it will be a beta-1 release. If not, it will be an
>>> alpha-1 release with an appropriate warning in the release notes about
>>> subject to change etc. While it is important to get macros correct, I
>>> fear that having a release is probably the only way to get enough
>>> eyeballs/attention to catch any unforeseen impacts of that change.
>>>
>>> Any thoughts?
>>>
>>
>> I agree, I think it would be good to get a 2.5 alpha/beta out soon to get
>> more eyes on macros and the many other changes not in 2.4.
>>