Mailing-List: contact dev-help@groovy.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@groovy.apache.org
MIME-Version: 1.0
In-Reply-To: <CAMbkE7SQ8H-mS0Tt-3YAaoezAPNhaMur65GU+dzu0OOirnDZ_Q@mail.gmail.com>
References: <CAMbkE7SQ8H-mS0Tt-3YAaoezAPNhaMur65GU+dzu0OOirnDZ_Q@mail.gmail.com>
From: John Wagenleitner <john.wagenleitner@gmail.com>
Date: Thu, 9 Mar 2017 06:10:37 -0800
Message-ID: <CAHPL-JkSmNZYAsUW5JrhHZWO3753ERHb9g515Wx_Y19Z=OLQLw@mail.gmail.com>
Subject: Re: upcoming releases
To: dev@groovy.apache.org
Content-Type: multipart/alternative; boundary=94eb2c08301233f73b054a4ccf3a
archived-at: Thu, 09 Mar 2017 14:16:14 -0000

--94eb2c08301233f73b054a4ccf3a
Content-Type: text/plain; charset=UTF-8

On Tue, Mar 7, 2017 at 1:40 PM, Paul King <paulk@asert.com.au> wrote:

> Hi,
>
> I am planning to merge PR#508 and start the release process for 2.4.10
> over the next few days. This contains an important bug fix that
> affects downstream projects such as Grails. Any other fixes people
> want in that release?
>
> Soon after that is released I am planning to create a 2_5_X branch and
> begin preparation of a 2.5.0 release. If our review/rework of macros
> is complete by then it will be a beta-1 release. If not, it will be an
> alpha-1 release with an appropriate warning in the release notes about
> subject to change etc. While it is important to get macros correct, I
> fear that having a release is probably the only way to get enough
> eyeballs/attention to catch any unforeseen impacts of that change.
>
> Any thoughts?
>
>
I agree, I think it would be good to get a 2.5 alpha/beta out soon to get
more eyes on macros and the many other changes not in 2.4.

--94eb2c08301233f73b054a4ccf3a
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On T=
ue, Mar 7, 2017 at 1:40 PM, Paul King <span dir=3D"ltr">&lt;<a href=3D"mail=
to:paulk@asert.com.au" target=3D"_blank">paulk@asert.com.au</a>&gt;</span> =
wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bord=
er-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
I am planning to merge PR#508 and start the release process for 2.4.10<br>
over the next few days. This contains an important bug fix that<br>
affects downstream projects such as Grails. Any other fixes people<br>
want in that release?<br>
<br>
Soon after that is released I am planning to create a 2_5_X branch and<br>
begin preparation of a 2.5.0 release. If our review/rework of macros<br>
is complete by then it will be a beta-1 release. If not, it will be an<br>
alpha-1 release with an appropriate warning in the release notes about<br>
subject to change etc. While it is important to get macros correct, I<br>
fear that having a release is probably the only way to get enough<br>
eyeballs/attention to catch any unforeseen impacts of that change.<br>
<br>
Any thoughts?<br><br></blockquote><div><br></div><div>I agree, I think it w=
ould be good to get a 2.5 alpha/beta out soon to get more eyes on macros an=
d the many other changes not in 2.4.</div></div><br></div></div>

--94eb2c08301233f73b054a4ccf3a--