groovy-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Guillaume Laforge <glafo...@gmail.com>
Subject Re: Release 2.4.6 and 2.5.0-beta?
Date Thu, 04 Feb 2016 17:18:29 GMT
Cédric, Jochen, what do you think of this one?

On Thu, Feb 4, 2016 at 5:12 PM, Shil Sinha <shil.sinha@gmail.com> wrote:

> Side note: have all the bugfixes been backported? I think we talked about
>> a bugfix that was only on master recently.
>
>
>
> If you're referring to the issue mentioned in
> http://mail-archives.apache.org/mod_mbox/groovy-users/201601.mbox/browser
> (GROOVY-7705 <https://issues.apache.org/jira/browse/GROOVY-7705>), I
> chose not to backport my changes because they seemed to be more of an
> enhancement to the static compiler than a bugfix. However, as I said in
> that thread, I wouldn't be opposed to backporting the changes if other
> committers think it makes sense.
>
> On Tue, Feb 2, 2016 at 6:11 PM, Cédric Champeau <cedric.champeau@gmail.com
> > wrote:
>
>> I'm sorry about this. I'd like to repeat myself too: I'd like to see a
>> release ASAP too. Agendas are the way they are. Marco is trying to help us,
>> but didn't manage to find time to do so. At this point I'm tempted to try a
>> release the old way, but I need some time. I'm travelling this week and
>> will be on vacation next week, so almost impossible for me.
>>
>> Side note: have all the bugfixes been backported? I think we talked about
>> a bugfix that was only on master recently.
>>
>> 2016-02-02 22:23 GMT+01:00 John Wagenleitner <john.wagenleitner@gmail.com
>> >:
>>
>>> I just ran into GROOVY-7742 [1] that affects both master and
>>> GROOVY_2_4_X branches.  I marked it as a blocker since it may have pretty
>>> widespread impact, but I could be wrong so hope others will review.  Ran
>>> into the issue trying to use master to build Grails.  There have been quite
>>> a number of fixes in both branches and so will try to do some more testing
>>> against the bigger Groovy projects out there to verify.
>>>
>>> The other two JIRA issues marked as blockers have been around a while
>>> and so might be worth downgrading (i.e., don't think they'd hold up any
>>> releasing).
>>>
>>> [1] https://issues.apache.org/jira/browse/GROOVY-7742
>>>
>>> On Tue, Feb 2, 2016 at 11:15 AM, Shil Sinha <shil.sinha@gmail.com>
>>> wrote:
>>>
>>>> Another month without a release. :(
>>>>> I'm repeating myself, but we really should release 2.4.6. In another
>>>>> month the last bugfix release will be half a year ago.
>>>>> We should also release 2.5-beta, it may lack flashy features (beside
>>>>> the macro-stuff), but 2.4 was released over a year ago and 2.5 contains
a
>>>>> lot nice enhancements and important bugfixes.
>>>>
>>>>
>>>> For the reasons Pascal mentioned, I think this deserves more attention
>>>> at this point. Is there a discrete list of things left to do?
>>>>
>>>> On Tue, Feb 2, 2016 at 1:51 PM, Pascal Schumacher <
>>>> pascalschumacher@gmx.net> wrote:
>>>>
>>>>> Another month without a release. :(
>>>>>
>>>>> I'm repeating myself, but we really should release 2.4.6. In another
>>>>> month the last bugfix release will be half a year ago.
>>>>>
>>>>> We should also release 2.5-beta, it may lack flashy features (beside
>>>>> the macro-stuff), but 2.4 was released over a year ago and 2.5 contains
a
>>>>> lot nice enhancements and important bugfixes.
>>>>>
>>>>> Am 06.01.2016 um 09:12 schrieb Cédric Champeau:
>>>>>
>>>>>> FYI, Marco Vermeulen is going to work on scripts that are aimed
>>>>>> towards simplifying release process. As it is hardly possible now,
we're
>>>>>> likely going to abandon releasing from TeamCity, and rely on Gradle
build
>>>>>> scripts instead. Stay tuned.
>>>>>>
>>>>>> Am 02.01.2016 um 17:10 schrieb Pascal Schumacher:
>>>>> > As I was not present at the conference I can not follow the
>>>>> discussion, but we should really release 2.4.6. There now there are 61
>>>>> issues fixed:
>>>>> >
>>>>> >
>>>>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20GROOVY%20AND%20fixVersion%20%3D%202.4.6%20ORDER%20BY%20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC
>>>>> >
>>>>> > The last release was 3 and a half months ago. :( Anything I can
do
>>>>> to help get 2.4.6 out of the door?
>>>>> >
>>>>> > I also think we should release a 2.5 beta soon.
>>>>>
>>>>>
>>>>
>>>
>>
>


-- 
Guillaume Laforge
Apache Groovy committer & PMC member
Product Ninja & Advocate at Restlet <http://restlet.com>

Blog: http://glaforge.appspot.com/
Social: @glaforge <http://twitter.com/glaforge> / Google+
<https://plus.google.com/u/0/114130972232398734985/posts>

Mime
View raw message