FYI, vote has been restarted: http://www.mail-archive.com/[email protected]/msg33376.html
General consensus was to re-stage the fixed build as 2.5.0 On 23 Jun 2014, at 12:41, Stuart McCulloch <[email protected]> wrote: > On 23 Jun 2014, at 08:11, Stuart McCulloch <[email protected]> wrote: > >> On 23 Jun 2014, at 03:25, "Mark Derricutt" <[email protected]> wrote: >> >>> 2.5.0? What happened to to 2.4.1-SNAPSHOT that we're testing here? Or has >>> 2.4.1-SNAPSHOT turned into 2.5.0-SNAPSHOT? >> >> It was staged as 2.5.0 following this discussion on the dev list: >> http://www.mail-archive.com/[email protected]/msg33273.html since it >> contains new features >> >>> Sounds like this is a rather fundamentally breaking bug which should >>> probably halt the release... >> >> Versions are cheap - if we decide to restage then I'd still lean towards >> staging this bugfix as 2.5.1 unless anyone had any strong objections >> >> And if we decide to release 2.5.0 (depends how many use cases this affects) >> then 2.5.1 won't be far away. > > I’ve recreated the issue with a basic project, so have cancelled the release > vote until this is fixed. > >>> On 23 Jun 2014, at 12:09, Stuart McCulloch wrote: >>> >>>> Log an issue and I'll schedule it for 2.5.1 (the vote for 2.5.0 is already >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [email protected] >>> For additional commands, e-mail: [email protected]
