groovy-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Paul King <pa...@asert.com.au>
Subject Re: Preparing for a release
Date Wed, 17 Feb 2016 04:20:54 GMT
I looked into what would be needed to backport GROOVY-7427 and it
turns out we'd need to bring across half of GROOVY-7087 as well. So,
while it can be done, I am kind of -1 on such a change and +1 on
getting the 2.5 beta out.

Cheers, Paul.

On Wed, Feb 17, 2016 at 8:29 AM, C├ędric Champeau
<cedric.champeau@gmail.com> wrote:
> For Groovy Eclipse we have no choice: the Eclipse compiler is a fork of the
> Groovy compiler with Eclipse specific code. That's just how it works: new
> Groovy version, new Groovy Eclipse version.
>
> 2016-02-16 22:56 GMT+01:00 chrylis <christopher.smith@artsquare.com>:
>>
>> > Keeping small backwards compatible enhancements out of bugfix releases
>> > is good as long as there are frequent non-bugfix releases.
>>
>> Do you consider all micros to be "bugfix releases", or are some of them
>> fixes and some of them small enhancements? In Groovy, there's a tendency
>> for
>> minor updates to require cascading changes to other components (e.g.,
>> GRECLIPSE, Spock).
>>
>>
>>
>> --
>> View this message in context:
>> http://groovy.329449.n5.nabble.com/Preparing-for-a-release-tp5731147p5731203.html
>> Sent from the Groovy Dev mailing list archive at Nabble.com.
>
>

Mime
View raw message