+1 (binding)

On 11.01.20 22:27, Guillaume Laforge wrote:
+1 (binding)

On Sat, Jan 11, 2020 at 10:26 PM Remko Popma <remko.po...@gmail.com
<mailto:remko.po...@gmail.com>> wrote:

    +1

    On Sat, Jan 11, 2020 at 12:14 PM Paul King <pa...@asert.com.au
    <mailto:pa...@asert.com.au>> wrote:
     >
     >
     > Dear development community,
     >
     > I am happy to start the VOTE thread for a Groovy 2.4.18 bug fix
    release!
     >
     > This release includes 3 bug fixes/improvements as outlined in the
    changelog:
     >
    
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123&version=12345496
     >
     > Tag:
    
https://gitbox.apache.org/repos/asf?p=groovy.git;a=tag;h=refs/tags/GROOVY_2_4_18
     > Tag commit id: ee00dd257711390ecac3c5a3823db428a9a72a26
     >
     > The artifacts to be voted on are located as follows (r37563).
     > Source release:
    https://dist.apache.org/repos/dist/dev/groovy/2.4.18/sources
     > Convenience binaries:
    https://dist.apache.org/repos/dist/dev/groovy/2.4.18/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 2.4.18.
     >
     > 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 2.4.18
     > [ ]  0 I don't have a strong opinion about this, but I assume it's ok
     > [ ] -1 Do not release Apache Groovy 2.4.18 because...
     >
     > Here is my vote:
     >
     > +1 (binding)
     >



--
Guillaume Laforge
Apache Groovy committer
Developer Advocate @ Google Cloud Platform

Blog: http://glaforge.appspot.com/
Twitter: @glaforge <http://twitter.com/glaforge>

Reply via email to