A 2.5 BETA release would be fantastic, if possible!
- has the (new apache) release process been automated?
- can we have regular (automated) releases? e.g. monthly?
NickOn Wed, 25 May 2016 05:46 Cédric Champeau <firstname.lastname@example.org> wrote:I'll do it.2016-05-21 6:43 GMT+02:00 Andrew Bayer <email@example.com>:It'd be really great if we could get 2.4.7 out in the next week or so in order to make it into the first Jenkins 2.x LTS - do we have a release manager to shepherd it through?A.On Fri, May 20, 2016 at 7:33 AM, Cédric Champeau <firstname.lastname@example.org> wrote:We can't. There are rules, now :)2016-05-20 16:31 GMT+02:00 Søren Berg Glasius <email@example.com>:Live releasing at GR8Conf ! ;) That's what Andres Almiray usually do.
Søren Berg Glasius
Hedevej 1, Gl. Rye, 8680 Ry, Denmark
Mobile: +45 40 44 91 88, Skype: sbglasius
--- Press ESC once to quit - twice to save the changes.
From: Cédric Champeau <firstname.lastname@example.org>
Reply: email@example.com <firstname.lastname@example.org>
Date: May 20, 2016 at 16:28:13
To: email@example.com <firstname.lastname@example.org>
Subject: Re: 2.4.7 Release?
That's enough for a release I would say :)
2016-05-20 16:25 GMT+02:00 Daniel Spilker <email@example.com>:
According to JIRA, these issues have been resolved: https://issues.apache.org/jira/issues/?jql=project%20%3D%20GROOVY%20AND%20fixVersion%20%3D%202.4.7
On Fri, May 20, 2016 at 3:25 PM, Cédric Champeau <firstname.lastname@example.org> wrote:
A new release would be timely. Maybe we can try to get the 2.5 beta out too, would be nice for GR8Conf!What other fixes are in 2.4.7?
2016-05-20 14:34 GMT+02:00 Guillaume Laforge <email@example.com>:
I've just updated the issue.
On Fri, May 20, 2016 at 2:23 PM, Daniel Spilker <firstname.lastname@example.org> wrote:
Hi Guillaume,the "Affects Version" in GROOVY-7826 is not exact. As the original reporter mentioned in a comment , this problem has been introduced in 2.2.0-beta-2 and I can confirm this. The commit which (indirectly) introduced the problem is
74089c1 . So we would need to downgrade to 2.1.9, which would be a huge step back. OK, not compared to 1.8.9, but still...
The git tag for 2.2.0-beta-2 is missing, but there is a tag named GROOVY_2_0_0_BETA_2  pointing to the commit which sets the version to 2.2.0-beta-2. Can you fix that?Daniel
And can you fix the "Affects Version" in JIRA? I do not have permission to edit the issue.
On Fri, May 20, 2016 at 11:35 AM, Guillaume Laforge <email@example.com> wrote:
Hi Daniel,No immediate plan for the moment.If GROOVY-7826 is a regression only since 2.4.5, perhaps you could migrate to 2.4.5 (considering you're migrating from the old 1.8.9) till we make a release of 2.4.7?Guillaume--
On Thu, May 19, 2016 at 9:01 PM, Daniel Spilker <firstname.lastname@example.org> wrote:
DanielRegards,I'm asking because we updated to 2.4.6 in Jenkins 2.0 (from 1.8.9) and hit a regression with GROOVY-7826. It would be nice to have a new 2.4 release for the first Jenkins 2.x LTS release which will be cut in ~2 weeks.Hi,is there a plan to release 2.4.7 anytime soon? It's been 3 month since 2.4.6 and there have been a lot of improvements in 2.4.x.