Re: Vote for a 2.5 BETA release
In terms of process, I think normally we prepare the release artefacts and vote on release of those artefacts. Cheers, Paul. On Fri, Sep 23, 2016 at 3:01 AM, Jochen Theodorouwrote: > > +1 > > following apache tradition this vote has to be at least 72h long... a > timespan we will need anyway to bridge the javaone caused gap ;) > > bye Jochen >
Re: Vote for a 2.5 BETA release
+1 following apache tradition this vote has to be at least 72h long... a timespan we will need anyway to bridge the javaone caused gap ;) bye Jochen
Vote for a 2.5 BETA release
There's been a lot of talk, a few questions but afaik no explicit vote for the 2.5 BETA release... so here it is. Last I heard <http://mail-archives.apache.org/mod_mbox/groovy-dev/201603.mbox/%3ccaj2hcd_hupv-9rkg2fvjlezwwnekpdbvhn36nyx7ivunxid...@mail.gmail.com%3E>, the consensus was to have a release without macro documentation. I'd like to start of the voting process with a +1. Kind regards, Nick Grealy (Otherwise... can I get GROOVY-7423 <https://issues.apache.org/jira/browse/GROOVY-7423> into the 2.4.8 release before it's released? A year and a half to wait for a change is getting ridiculous IMO).