Thank you all for participating the vote! I'll revise the release and put up another vote soon.
To be fixed: * giraph-examples.jar (fixed in BIGTOP-2908 <https://issues.apache.org/jira/browse/BIGTOP-2908>) * PPC64LE repos (fixed in BIGTOP-2903 <https://issues.apache.org/jira/browse/BIGTOP-2903>) Thanks Kevin for quick patches. Something I'm confused: - sha1 (the file is malformed, which makes sha1sum -c impossible) (passed) I have tested this and it seems the sha1 of bigtop-1.2.1-project.tar.gz.sha1 matches what contained in bigtop-1.2.1-project.tar.gz.sha1. Can you elaborate the problem? 2017-10-19 5:01 GMT+08:00 Konstantin Boudnik <c...@apache.org>: > +1 on the release note addition. > > On Wed, Oct 18, 2017 at 03:34PM, Kevin Monroe wrote: > > Roger that Cos. In a separate thread, Evans mentioned that ppc64le > > convenience artifacts can be uploaded later.. My objection is that > ppc64le > > users may want to try the new release on announce, yet be discouraged > when > > the repos aren't able to deliver. > > > > Let's at least call this out in the release notes. Thanks! > > -Kevin > > > > On Wed, Oct 18, 2017 at 3:12 PM, Konstantin Boudnik <c...@apache.org> > wrote: > > > > > I see where you're going, Kev. But stricktly speaking, we are only > voting > > > on > > > the source code of the release. Binaries are provided for the > convenience > > > only. > > > > > > Thanks, > > > Cos > > > > > > On Wed, Oct 18, 2017 at 03:07PM, Kevin Monroe wrote: > > > > -1 > > > > > > > > AFAICT, it is not possible to deploy 1.2.1 on ppc64le because there > are > > > no > > > > binaries for that arch in the repo. While my vote isn't binding, it > > > feels > > > > wrong that we would release 1.1.0 and 1.2.0 with this arch, yet make > it > > > > unavailable for 1.2.1. > > > > > > > > Good repo in 1.2.0: > > > > http://bigtop-repos.s3.amazonaws.com/releases/1.2.0/ > ubuntu/16.04/ppc64le > > > > > > > > Bad repo in 1.2.1: > > > > http://repos.bigtop.apache.org/releases/1.2.1/ubuntu/16.04/ppc64le > > > > > > > > Specific error for 1.2.1 on ppc64le: > > > > E: Failed to fetch > > > > http://repos.bigtop.apache.org/releases/1.2.1/ubuntu/16. > > > 04/ppc64le/dists/bigtop/contrib/binary-ppc64el/Packages > > > > 404 Not Found > > > > > > > > Thanks, > > > > -Kevin > > > > > > > > On Thu, Oct 12, 2017 at 2:30 PM, Evans Ye <evan...@apache.org> > wrote: > > > > > > > > > This is the vote for release 1.2.1 of Apache Bigtop. > > > > > > > > > > It fixes the following issues: > > > > > > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa? > > > > > version=12340373&projectId=12311420 > > > > > > > > > > The vote will be going for at least 72 hours and will be closed on > > > Sunday, > > > > > October 15th, 2017 at noon PDT. Please download, test and vote > with > > > > > > > > > > [ ] +1, accept RC1 as the official 1.2.1 release of Apache Bigtop > > > > > [ ] +0, I don't care either way, > > > > > [ ] -1, do not accept RC1 as the official 1.2.1 release of Apache > > > Bigtop, > > > > > because... > > > > > > > > > > Source and binary files: > > > > > https://dist.apache.org/repos/ > dist/dev/bigtop/bigtop-1.2.1- > > > RC1/ > > > > > > > > > > Maven staging repo: > > > > > https://repository.apache.org/content/repositories/ > > > orgapachebigtop-1015 > > > > > > > > > > The git tag to be voted upon is release-1.2.1-RC1 > > > > > > > > > > Bigtop's KEYS file containing PGP keys we use to sign the release: > > > > > https://dist.apache.org/repos/dist/release/bigtop/KEYS > > > > > > > > >
