+1 On Sun, Aug 21, 2016 at 5:34 AM heith seewald <hei...@gmail.com> wrote:
> +1 > > > > On Sat, Aug 20, 2016 at 5:57 PM, Dave Brondsema <d...@brondsema.net> > wrote: > > > Its been 72 hours, but since its the weekend I'll wait a couple more > > days if anyone else wants to vote. > > > > On 08/17/2016 04:14 PM, Dave Brondsema wrote: > > > Hello, > > > > > > This is a call for a vote on Apache Allura 1.5.0. > > > > > > Source tarball, signature and checksums are available at: > > > https://dist.apache.org/repos/dist/dev/allura/ > > > > > > Checksums: > > > MD5: 86db4a009a55b6cd1a99d91e2361dd09 allura-1.5.0.tar.gz > > > SHA1: db7351679392a44101d30c8c676c8318ebae3eda allura-1.5.0.tar.gz > > > SHA512: > > > 23581e6fb756e0d4098f6112e5f937c7ddfa82b9a763f03d4803664fe0c4 > > 5a1db5dd73febe347580b5014825b673a9b06848b3b8c53d01dc4c70fb06096493ff > > > allura-1.5.0.tar.gz > > > > > > The KEYS file can be found at: > > > http://www.apache.org/dist/allura/KEYS > > > > > > The release has been signed with key (9BB3CE70): > > > http://pgp.mit.edu:11371/pks/lookup?op=vindex&search= > > 0x56F0526F9BB3CE70 > > > > > > Source corresponding to this release can be found at: > > > Commit: 4155220ef5eefa6aee843b6c7e3fda7590a23110 > > > Tag: rel/1.5.0 (pending successful vote) > > > Browse: > > > https://forge-allura.apache.org/p/allura/git/ci/ > > 4155220ef5eefa6aee843b6c7e3fda7590a23110/log/ > > > > > > Changes for this version are listed at: > > > > > > https://forge-allura.apache.org/p/allura/git/ci/ > > 4155220ef5eefa6aee843b6c7e3fda7590a23110/tree/CHANGES > > > > > > The RAT license report is available at: > > > https://forge-allura.apache.org/p/allura/pastebin/ > > 57b4b87f6d19cd6b996302bc > > > > > > Vote will be open for at least 72 hours (Sat, 20 Aug 2016 14:45:24 > > UTC). Votes > > > from Allura PMC members are binding, but we welcome all community > > members to > > > vote as well. For the new PMC members among us, > > > https://forge-allura.apache.org/p/allura/wiki/ASF% > > 20Release%20Guidelines/ has a > > > list of guidelines of various things we should make sure are in order > > for a > > > release. We got them all set when the project was getting started in > > the Apache > > > Incubator, so now we pretty much just have to make sure we don't make > > incorrect > > > changes to the LICENSE or forget to add something, etc. > > > > > > I've only done some basic tests so far, I will cast my vote after I go > > through a > > > fresh docker setup with this release candidate. > > > > > > > > > [ ] +1 approve > > > [ ] +0 no opinion > > > [ ] -1 disapprove (and reason why) > > > > > > Thanks & Regards > > > > > > > > > -- > > Dave Brondsema : d...@brondsema.net > > http://www.brondsema.net : personal > > http://www.splike.com : programming > > <>< > > >
