I ran all the tests and did my usual smoke tests with the console, and everything went well.
+1 (binding) Guillaume On Sun, Jul 7, 2019 at 7:27 PM Daniel.Sun <sun...@apache.org> wrote: > Dear development community, > > I am happy to start the VOTE thread for a Groovy 3.0.0-beta-2 release! > > This release includes 40 bug fixes/improvements as outlined in the > changelog: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123&version=12345498 > > Tag: > > https://gitbox.apache.org/repos/asf?p=groovy.git;a=tag;h=refs/tags/GROOVY_3_0_0_BETA_2 > Tag commit id: ca8205f62726af165ac396be1bbfaa194aed482c > > The artifacts to be voted on are located as follows (r34788). > Source release: > https://dist.apache.org/repos/dist/dev/groovy/3.0.0-beta-2/sources > Convenience binaries: > https://dist.apache.org/repos/dist/dev/groovy/3.0.0-beta-2/distribution > > Release artifacts are signed with a key from the following file: > https://dist.apache.org/repos/dist/dev/groovy/KEYS > > Please vote on releasing this package as Apache Groovy 3.0.0-beta-2. > > Reminder on ASF release approval requirements for PMC members: > http://www.apache.org/legal/release-policy.html#release-approval > Hints on validating checksums/signatures (but replace md5sum with > sha256sum): > https://www.apache.org/info/verification.html > > The vote is open for the next 72 hours and passes if a majority of at least > three +1 PMC votes are cast. > > [ ] +1 Release Apache Groovy 3.0.0-beta-2 > [ ] 0 I don't have a strong opinion about this, but I assume it's ok > [ ] -1 Do not release Apache Groovy 3.0.0-beta-2 because... > > Here is my vote: > > +1 (binding) > > > > > ----- > Apache Groovy committer & PMC member > Blog: http://blog.sunlan.me > Twitter: @daniel_sun > > -- > Sent from: http://groovy.329449.n5.nabble.com/Groovy-Dev-f372993.html > -- Guillaume Laforge Apache Groovy committer Developer Advocate @ Google Cloud Platform Blog: http://glaforge.appspot.com/ Twitter: @glaforge <http://twitter.com/glaforge>
