This is more or less a dup to BIGTOP-1916. But I am unsure if I should update this *now* since the URL to 1.0.0 release is not valid .
Olaf > Am 10.08.2015 um 01:59 schrieb Konstantin Boudnik <[email protected]>: > > A small update: > The URL to the KEYS at the botton has the old version of the KEYS file > > Please use > https://dist.apache.org/repos/dist/release/bigtop/KEYS > instead, while I am working with INFRA on updating the dist one. > > Thank you > Cos > > On Sat, Aug 08, 2015 at 03:51AM, Konstantin Boudnik wrote: >> This is the vote for release 1.0.0 of Apache Bigtop. >> >> It fixes the following issues: >> >> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12326837&styleName=Text&projectId=12311420 >> >> This is the respin of RC3, addressing the fix for default repo uRLs and >> adding >> proper header licenses to be able to run full RAT check on the release. >> The rest of the release is the same. >> >> The vote will be going for at least 48 hours and will be closed on >> Tuesday August 11th, 2015 at noon PDT. Please download, test and vote with >> >> [ ] +1, accept RC4 as the official 1.0.0 release of Apache Bigtop >> [ ] +0, I don't care either way, >> [ ] -1, do not accept RC4 as the official 1.0.0 release of Apache Bigtop, >> because... >> >> Source and binary files: >> http://people.apache.org/~cos/bigtop-1.0.0-RC4 >> >> Maven staging repo: >> >> https://repository.apache.org/content/repositories/orgapachebigtop-1004 >> >> The git tag to be voted upon is release-1.0.0 >> >> Bigtop's KEYS file containing PGP keys we use to sign the release: >> http://svn.apache.org/repos/asf/bigtop/dist/KEYS >> > >
signature.asc
Description: Message signed with OpenPGP using GPGMail
