Re: [EXT] Next releases

that do not fix broken functionality in a point release. From: Paul King Sent: Sunday, June 23, 2024 7:27 PM To: Groovy_Developers Subject: [EXT] Next releases External Email: Use caution with links and attachments. Hi folks, I'd like to roll out another round

Next releases

Hi folks, I'd like to roll out another round of releases later in the week. Time to get in any outstanding changes or let me know if there is something we need to wait for. Cheers, Paul.

Next releases

Hi folks, I'd like to do another 4 & 5 release over the weekend or early next week. Mostly just to get the JDK23 support out. Time to finish up any changes you might be working on, but also let me know if you have any changes that we should really wait for. Thanks, Paul.

Re: Next releases

Hi folks, Eric did spot a couple of regressions that crept into the releases despite our best efforts, but we think they shouldn't impact most users. I'll go ahead with releases as planned but we'll probably do another round of releases in a couple of weeks. Please do try out the releases and

Next releases

Hi folks, I'll kick off another round of releases next week. Make any changes you need or let me know if there is anything we should be awaiting for. Currently, I am thinking of the next alpha for 5 and a bump of 3 and 4. Cheers, Paul.

Re: Next releases

The 5.0.0-alpha-5 release is delayed. One of the few tasks I didn't check when we upgraded to Gradle 8.5 was maven publishing. That isn't working, e.g.: * What went wrong: Execution failed for task ':publishMavenPublicationToLocalFileRepository'. > Failed to publish publication 'maven' to

Next releases

Hi folks, I was going to release another Groovy 4.0.x and 5 alpha version in the coming days. Time to get in any fixes or let me know if there is stuff coming which we should wait for. Cheers, Paul.

Re: next releases

On 11.12.23 22:11, Paul King wrote: Hi folks, I was planning to do one more round of releases before the end of the year. Let me know what might need to be done before I hit the go button. It would need to be done in about a week (to get in before Christmas) or I'd probably aim for around the

next releases

Hi folks, I was planning to do one more round of releases before the end of the year. Let me know what might need to be done before I hit the go button. It would need to be done in about a week (to get in before Christmas) or I'd probably aim for around the 27th to get in before the new year.

Next releases

Hi folks, I was planning to kick off some more releases over the weekend or first thing next week. Time to propose/commit any changes that you require, or let me know if there is anything major that I should hold off for. I am not sure how much time I will have but I will include at least a

Next releases

Hi folks, I'll probably try to do some releases early next week (at least 4.0.15 and another 5 alpha release). Time to get in your fixes or let me know if I need to wait for something important. Cheers, Paul.

Next releases

Hi all, I will try to kick off the next round of releases probably at the end of this week. Time to get in any needed changes or let me know if there is anything we should wait for. Cheers, Paul.

Re: Next releases

Our build process is impacted by: https://status.gradle.com/incidents/7x4wqd7zv715 Investigating - Without any prior announcement, it looks like JCenter is > now redirecting to Maven Central instead of serving artifacts. > Builds that have build logic that relies on artifacts available only on >

Next releases

Hi folks, I will likely roll out 3.0.x and 4.0.x releases late in the week or over the coming weekend. Time to get in any fixes or let me know if there is something we should wait for. Cheers, Paul.

next releases

Hi folks, I'll kick off another round of releases soon. Time to get any changes in now or let me know if there is a reason to delay. Cheers, Paul.

RE: [EXT] Next releases

> quite a lot of changes are required to support Java 16+ Yes, for proper proxy and default method support there are a lot of changes. Not asking for a backport on that stuff. ASM 9.4 is required to parse the class files created by Java 19 target. FYI, I updated ASM from 9.3 to 9.4 for

RE: [EXT] Next releases

AFAIR, quite a lot of changes are required to support Java 16+, ASM update is just one of the changes. Cheers, Daniel Sun On 2023/01/12 18:51:37 "Milles, Eric (TR Technology) via dev" wrote: > I had a developer comment that Java 19 required an update from Groovy 3 to > Groovy 4 (due to ASM).

RE: [EXT] Next releases

I had a developer comment that Java 19 required an update from Groovy 3 to Groovy 4 (due to ASM). Where are we with regards to ASM versions for Groovy 2.5, 3.0, 4.0 and 5.0?

Next releases

I'm looking to do 4.0.8 and a bump on 2.5 some time in the next few days. Anything else needed before I hit the go button?

Re: next releases ...

I have no major changes for the branches listed. Cheers, Daniel Sun On 2022/11/21 02:26:29 Paul King wrote: > Hi folks, > > I plan to do some more releases soon (2.5, 3.0 and 4.0 branches). Time > to get in any fixes you need or let me know if there is something we > should be waiting for. > >

Re: next releases ...

I was hoping to progress releases this week but I have numerous things still to check, so I'll continue checking next week and start the releases after that. Cheers, Paul. On Mon, Nov 21, 2022 at 12:26 PM Paul King wrote: > > Hi folks, > > I plan to do some more releases soon (2.5, 3.0 and 4.0

next releases ...

Hi folks, I plan to do some more releases soon (2.5, 3.0 and 4.0 branches). Time to get in any fixes you need or let me know if there is something we should be waiting for. Thanks, Paul.

Next releases

Hi folks, I'll probably do a 4.0.6 release to pick up a handful of fixes there as well as a bump on the 2.5 branch. I'll target some time during the coming week. Please get in any changes you want or let me know if there is something in particular that you think we need to get in. Cheers, Paul.

Next releases

Hi Folks, I might do some more releases soon. Time to get in any fixes which you need for the next versions. Or shout if you believe something else still needs to be done. Cheers, Paul.

Planning for next releases

Hi folks, We have 34, 13, & 4 fixes for upcoming 4.0.4, 3.0.12, & 2.5.18 potential releases: https://issues.apache.org/jira/projects/GROOVY/versions/12351811 https://issues.apache.org/jira/projects/GROOVY/versions/12351799 https://issues.apache.org/jira/projects/GROOVY/versions/12351798 It's

Next releases

Hi folks, I was probably going to do another round of releases either later this week or shortly thereafter. Including 4.0.3 but possibly also 3 and 2.5 bumps. Tie to get in any fixes or provide feedback. Cheers, Paul.

RE: Next releases

Will the next 3.0.x release support Java 17? Specifically GROOVY-10201 is still open. /peter -Original Message- From: Paul King Sent: Monday, February 28, 2022 6:44 AM To: Groovy_Developers Subject: Next releases Hi folks, I was looking to do a 4.0.1 release and bumps for the 3.0.x

Re: Next releases

Is there something like a 4.0.1-rc-1 or similar artifact I could try? On Mon, Feb 28, 2022 at 3:13 PM Lóránt Pintér wrote: > I'm about to run another test with the latest to see if it works for > Gradle. I'll be able to say if the fixes so far have resolved all the > problems we encountered

Re: Next releases

I'm about to run another test with the latest to see if it works for Gradle. I'll be able to say if the fixes so far have resolved all the problems we encountered with our upgrade in a couple hours. On Mon, Feb 28, 2022 at 12:44 PM Paul King wrote: > Hi folks, > > I was looking to do a 4.0.1

Next releases

Hi folks, I was looking to do a 4.0.1 release and bumps for the 3.0.x and 2.5.x branches. Anyone have anything outstanding that needs to be included? Thanks, Paul.

Next releases

Hi folks, I hope to get some releases ready for voting in the next week. Time to get in any bug fixes you want in the next release. Probably 4.0.0-alpha-3 (possibly last alpha) and 3.0.8 but I may stagger them to allow better testing of the changes in the release scripts. Cheers, Paul.

Next releases ...

We have a few bug fixes clocked up against the various releases. I'll probably kick off some releases next week. Time to get in your priority fixes if you want to make the train. I'll do at least 3.0.7 and 2.5.14. Cheers, Paul.

Re: Next releases

Hi Paul, ASM 9.0 have been released this morning. regards, Rémi > De: "paulk" > À: "Remi Forax" > Cc: "dev" > Envoyé: Lundi 21 Septembre 2020 08:19:47 > Objet: Re: Next releases > Thanks for the update Rémi. I saw the version number comm

Re: Next releases

hopefully, this should be fixed soon. > > Rémi > > -- > > *De: *"paulk" > *À: *"dev" > *Envoyé: *Lundi 21 Septembre 2020 03:47:13 > *Objet: *Next releases > > > Hi everyone, > > I hope to make some more releases bef

Re: Next releases

ASM 9 should have been released this week end but we have an issue with our nexus requiring human intervention on the hardware, hopefully, this should be fixed soon. Rémi > De: "paulk" > À: "dev" > Envoyé: Lundi 21 Septembre 2020 03:47:13 > Objet: Next re

Re: Next releases

Forgot to mention, please ignore any test deployments to the staging area. I need to test out some jarjar changes and maven coordinate changes in the release scripts and will be rolling them back until we are ready for a real release. Cheers, Paul. On Mon, Sep 21, 2020 at 11:47 AM Paul King

Next releases

Hi everyone, I hope to make some more releases before ApacheCon @Home[1] starts in just over a week since we have quite a few fixes and improvements ready for release (we have over 60 fixes in 3.0.6 for instance). I'd like a Groovy 4.0.0-alpha-1, hopefully 3.0.6 and possibly 2.5.14. There are a

Re: next releases

Hi Paul, I have no more commits for the two releases. Cheers, Daniel Sun On 2020/07/01 22:41:28, Paul King wrote: > Hi everyone, > > I'd like to do another 2.5 and 3 release late this week or early next week. > Time to work on any bug fixes that you want included or let me know if the >

RE: next releases

: Re: next releases This issue causes a horrible experience with IntelliJ and groovy code annotated for bytecode generation with (e.g. Grails GORM, Micronaut, etc). https://issues.apache.org/jira/projects/GROOVY/issues/GROOVY-9209<https://nam02.safelinks.protection.outlook.com/?url=https%3A

Re: next releases

This issue causes a horrible experience with IntelliJ and groovy code annotated for bytecode generation with (e.g. Grails GORM, Micronaut, etc). https://issues.apache.org/jira/projects/GROOVY/issues/GROOVY-9209  On Thu, Jul 2, 2020 at 12:41 AM Paul King wrote: > > Hi everyone, > > I'd like

next releases

Hi everyone, I'd like to do another 2.5 and 3 release late this week or early next week. Time to work on any bug fixes that you want included or let me know if the timing doesn't work. Thanks, Paul.

Re: next releases

Il 14/05/20 03:58, Paul King ha scritto: Time to get in any bug fixes you want for those releases. Please also let me know if you have any issues with the proposed timeframe. Is it possible to backport GROOVY-9518 to 2.5.x? And maybe have a look at GROOVY-9523 and GROOVY-9524? Thanks, Mauro

Re: next releases

t; I was going to volunteer to prepare the next releases in a couple of > > days. Definitely 3.0.4, probably 2.5.12 and maybe our first alpha of 4.0 > > if I get time (or I may kick that off immediately after the others are > > complete). > > > > Time to get in any bug

Re: next releases

On 14.05.20 03:58, Paul King wrote: Hi everyone, I was going to volunteer to prepare the next releases in a couple of days. Definitely 3.0.4, probably 2.5.12 and maybe our first alpha of 4.0 if I get time (or I may kick that off immediately after the others are complete). Time to get in any

next releases

Hi everyone, I was going to volunteer to prepare the next releases in a couple of days. Definitely 3.0.4, probably 2.5.12 and maybe our first alpha of 4.0 if I get time (or I may kick that off immediately after the others are complete). Time to get in any bug fixes you want for those releases

Re: Next releases?

Hi Paul, It's OK to me. 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

Next releases?

Hi folks, I was planning to kick off 2.5.11 and 3.0.3 releases next week. Is that timing okay for everyone? Also, please contribute/assist get any crucial bug fixes that you need into those releases. Cheers, Paul.

Re: 答复: next releases

;> >> Maybe releasing 3.0.0-ea and 2.5.0-beta together suggested by >> Andres is feasible. >> >> >> >> Cheers, >> >> Daniel.Sun >> >> >> >> *发件人: *[hidden email] >> <http:///user/SendEmail.jtp?type=node=5737784=0> &g

Re: 答复: next releases

ing 3.0.0-ea and 2.5.0-beta together suggested by Andres > is feasible. > > > > Cheers, > > Daniel.Sun > > > > *发件人: *[hidden email] > <http:///user/SendEmail.jtp?type=node=5737784=0> > *发送时间: *2017年1月18日 6:42 > *收件人: *[hidden email] > <http:///

Re: next releases

On Tue, Jan 17, 2017 at 1:55 AM, Daniel Sun wrote: > Hi Andres, > > > I'd suggest to release 2.5.0-beta and 3.0-ea together. Just like the JDK > > team has been posting JDK9 EA releases, we could do the same. We know for > > a fact we're going to break things, so let's

Re: next releases

It's not a simple decision. A beta isn't something to play with. There are users, and companies, using Groovy. You cannot simply say "this is new, let's try this". There are backwards compatibility concerns, as well as deployment issues. We agreed, a few months ago, to make 3.0 the breaking

Re: next releases

On 17.01.2017 10:17, Russel Winder wrote: [...] The 2.5 build still creates jars and indy jars. Isn't it about time we settle this so there are only one set of jars in a build? right, we should also change to indy by default for the betas bye jochen

Re: next releases

On 17.01.2017 10:04, Cédric Champeau wrote: My take is simpler than this. If Parrot should be included in 2.5, then remove the old parser and use it. If it's for 3.0, then it should not belong to the 2.5 beta, or it should be an external dependency (possibly tested by adding a jar manually).

Re: next releases

On Tue, 2017-01-17 at 10:04 +0100, Cédric Champeau wrote: > My take is simpler than this. If Parrot should be included in 2.5, > then > remove the old parser and use it. If it's for 3.0, then it should not > belong to the 2.5 beta, or it should be an external dependency > (possibly > tested by

Re: next releases

luded in 2.5.x releases as an > optional parser? If developers want to give it a try, just turn on the > switch "-Dgroovy.antlr4=true". > > Cheers, > Daniel.Sun > > > > -- > View this message in context: > http://groovy.329449.n5.nabble.com/next-releases-tp

Re: next releases

ser? If developers want to give it a try, just turn on the > switch "-Dgroovy.antlr4=true". > > Cheers, > Daniel.Sun > > > > -- > View this message in context: http://groovy.329449.n5. > nabble.com/next-releases-tp5737758p5737761.html > Sent from the Groo

Re: next releases

+1 on all this :-) I'm impatient to have a beta of 2.5 out! Guillaume On Tue, Jan 17, 2017 at 3:09 AM, Paul King wrote: > I am thinking we should do a 2.5.0-beta-1 release and possibly a 2.4.9 > in a couple of weeks time. For 2.5.0-beta-1, it would be nice to have > the