I'm +1 on Andrés' plan. Let's have 2_4_X, 2_5_X and `master` for 3.0. Then it's much easier to do breaking changes on 3.0.

2017-01-18 1:16 GMT+01:00 Daniel Sun <realbluesun@hotmail.com>:

Hi Paul,

 

      OK. I understand others’s fears 😉 

      Maybe releasing 3.0.0-ea and 2.5.0-beta together suggested by Andres is feasible.

 

Cheers,

Daniel.Sun

 

发件人: [hidden email]
发送时间: 2017118 6:42
收件人: [hidden email]
主题: Re: next releases

 

Hi Daniel,

Other comments have kind of superseded this one. The only thing I'll
add is that I am not averse to finding a way to let 2.5 users try the
new parser somehow - but as Cédric said, not at the expensive of
overcomplicating our normal release.

Cheers, Paul.


On Tue, Jan 17, 2017 at 6:48 PM, Daniel Sun <[hidden email]> wrote:

> Hi Paul,
>
>       Will the new parser Parrot be included 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-tp5737758p5737761.html
> Sent from the Groovy Dev mailing list archive at Nabble.com.



If you reply to this email, your message will be added to the discussion below:
http://groovy.329449.n5.nabble.com/next-releases-tp5737758p5737780.html
To unsubscribe from next releases, click here.
NAML


View this message in context: 答复: next releases

Sent from the Groovy Dev mailing list archive at Nabble.com.