You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bigtop.apache.org by Evans Ye <ev...@apache.org> on 2017/10/12 18:30:44 UTC
[VOTE] Release Bigtop version 1.2.1
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
Re: [VOTE] Release Bigtop version 1.2.1
Posted by Bruno Mahé <bm...@apache.org>.
+1
On 10/17/2017 10:20 AM, Evans Ye wrote:
> My +1 of course.
>
> The vote is about to due so I encourage everyone with or without binding
> can chime in and give out your thoughts whenever it's in a good shape or not
>
> Evans Ye <ev...@apache.org>於 2017年10月15日 週日，下午2:45寫道：
>
>> This is definitely OK.
>> Let's extend the vote period until Wednesday, October 18th, 2017 at noon
>> PDT.
>>
>> 2017-10-15 11:22 GMT+08:00 Konstantin Boudnik <co...@apache.org>:
>>
>>> May I suggest to extend the vote until at least Tuesday considering a
>>> possible limited people availability over the weekend? I will be
>>> checking the release but I am away from the computer until Monday.
>>>
>>> We don't need to restart the vote, I am sure, if we extend it a little
>>> bit as nothing material gets changed. Thanks!
>>> --
>>> With regards,
>>> Konstantin (Cos) Boudnik
>>> 2CAC 8312 4870 D885 8616 6115 220F 6980 1F27 E622
>>>
>>> Disclaimer: Opinions expressed in this email are those of the author,
>>> and do not necessarily represent the views of any company the author
>>> might be affiliated with at the moment of writing.
>>>
>>>
>>> On Thu, Oct 12, 2017 at 11:30 AM, Evans Ye <ev...@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
>>
Re: [VOTE] Release Bigtop version 1.2.1
Posted by Evans Ye <ev...@apache.org>.
My +1 of course.
The vote is about to due so I encourage everyone with or without binding
can chime in and give out your thoughts whenever it's in a good shape or not
Evans Ye <ev...@apache.org>於 2017年10月15日 週日，下午2:45寫道：
> This is definitely OK.
> Let's extend the vote period until Wednesday, October 18th, 2017 at noon
> PDT.
>
> 2017-10-15 11:22 GMT+08:00 Konstantin Boudnik <co...@apache.org>:
>
>> May I suggest to extend the vote until at least Tuesday considering a
>> possible limited people availability over the weekend? I will be
>> checking the release but I am away from the computer until Monday.
>>
>> We don't need to restart the vote, I am sure, if we extend it a little
>> bit as nothing material gets changed. Thanks!
>> --
>> With regards,
>> Konstantin (Cos) Boudnik
>> 2CAC 8312 4870 D885 8616 6115 220F 6980 1F27 E622
>>
>> Disclaimer: Opinions expressed in this email are those of the author,
>> and do not necessarily represent the views of any company the author
>> might be affiliated with at the moment of writing.
>>
>>
>> On Thu, Oct 12, 2017 at 11:30 AM, Evans Ye <ev...@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
>>
>
>
Re: [VOTE] Release Bigtop version 1.2.1
Posted by Evans Ye <ev...@apache.org>.
This is definitely OK.
Let's extend the vote period until Wednesday, October 18th, 2017 at noon
PDT.
2017-10-15 11:22 GMT+08:00 Konstantin Boudnik <co...@apache.org>:
> May I suggest to extend the vote until at least Tuesday considering a
> possible limited people availability over the weekend? I will be
> checking the release but I am away from the computer until Monday.
>
> We don't need to restart the vote, I am sure, if we extend it a little
> bit as nothing material gets changed. Thanks!
> --
> With regards,
> Konstantin (Cos) Boudnik
> 2CAC 8312 4870 D885 8616 6115 220F 6980 1F27 E622
>
> Disclaimer: Opinions expressed in this email are those of the author,
> and do not necessarily represent the views of any company the author
> might be affiliated with at the moment of writing.
>
>
> On Thu, Oct 12, 2017 at 11:30 AM, Evans Ye <ev...@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
>
Re: [VOTE] Release Bigtop version 1.2.1
Posted by Konstantin Boudnik <co...@apache.org>.
May I suggest to extend the vote until at least Tuesday considering a
possible limited people availability over the weekend? I will be
checking the release but I am away from the computer until Monday.
We don't need to restart the vote, I am sure, if we extend it a little
bit as nothing material gets changed. Thanks!
--
With regards,
Konstantin (Cos) Boudnik
2CAC 8312 4870 D885 8616 6115 220F 6980 1F27 E622
Disclaimer: Opinions expressed in this email are those of the author,
and do not necessarily represent the views of any company the author
might be affiliated with at the moment of writing.
On Thu, Oct 12, 2017 at 11:30 AM, Evans Ye <ev...@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
Re: [VOTE] Release Bigtop version 1.2.1
Posted by Olaf Flebbe <of...@oflebbe.de>.
+1, But had only the chance to run one basic docker provisioner command. Checked Signatures.
> Am 12.10.2017 um 20:30 schrieb Evans Ye <ev...@apache.org>:
>
> 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
Re: [VOTE] Release Bigtop version 1.2.1
Posted by Konstantin Boudnik <co...@apache.org>.
Thanks for the great question and the detailed answer about the code mods vote!
The issue we have here is kinda on the fence: the issue is in the
code, but the vote is on the release. If you look at the same page but
under "Votes on Package Releases" you'll see that "...the 'minimum
quorum of three +1 votes' rule is universal." So, two +1 aren't
enough, as for release to be blessed by the PMC at least three votes
are required.
And no: binding votes aren't as twice as powerful ;) But only binding
votes are material when it gets to a release, because a project's PMC
is legally bound by the release decision. Hence, my -1 indicates that
we have a serious issue with inability to validate that all bits are
license clean. Which kills the release candidate.
That's how I see it.
--
With regards,
Konstantin (Cos) Boudnik
2CAC 8312 4870 D885 8616 6115 220F 6980 1F27 E622
Disclaimer: Opinions expressed in this email are those of the author,
and do not necessarily represent the views of any company the author
might be affiliated with at the moment of writing.
On Thu, Oct 19, 2017 at 3:36 PM, Kevin Monroe
<ke...@canonical.com> wrote:
> Hey Arnaud,
>
> I was looking into the ASF voting mechanism recently and came across this:
>
> https://www.apache.org/foundation/voting.html
>
> In this case, I think the relevant portion for a single -1 derailing the
> vote is here:
>
> ---
> Votes on code modifications follow a different model. In this scenario, a
> negative vote constitutes a veto , which cannot be overridden. Again, this
> model may be modified by a lazy consensus declaration when the request for
> a vote is raised, but the full-stop nature of a negative vote is unchanged.
> Under normal (non-lazy consensus) conditions, the proposal requires three
> positive votes and no negative ones in order to pass; if it fails to garner
> the requisite amount of support, it doesn't -- and typically is either
> withdrawn, modified, or simply allowed to languish as an open issue until
> someone gets around to removing it.
> ---
>
> As @cos mentioned earlier in the thread, the vote is on the bigtop code
> base and (to me) falls under the above code modification guidelines. He
> found a blocking RAT issue with the bigtop source and voted -1. There is
> no math that can dilute his veto.
>
> I'm far from an expert on ASF voting, but that's my read on why a binding
> -1 could block the release.
>
> -Kevin
>
> On Thu, Oct 19, 2017 at 3:29 PM, Arnaud Launay <as...@launay.org> wrote:
>
>> Le Fri, Oct 20, 2017 at 01:20:18AM +0800, Evans Ye a écrit:
>> > To summarize the vote result:
>> > The vote is REJECTED with 3 binding +1s, 1 binding -1 and 1 non-binding
>> -1.
>>
>> Just out of curiosity: 1 binding -1 is sufficient to derail the
>> vote ?
>>
>> Because to me, if you say something like "binding counts twice",
>> it goes :
>>
>> 3*(1*2)+1*(-1*2)+1*(1*-1)
>> 3
>>
>> Even with basic voting:
>> 3-1-1
>> 1
>>
>> Still positive ? :)
>>
>>
>> Arnaud.
>>
Re: [VOTE] Release Bigtop version 1.2.1
Posted by Kevin Monroe <ke...@canonical.com>.
Hey Arnaud,
I was looking into the ASF voting mechanism recently and came across this:
https://www.apache.org/foundation/voting.html
In this case, I think the relevant portion for a single -1 derailing the
vote is here:
---
Votes on code modifications follow a different model. In this scenario, a
negative vote constitutes a veto , which cannot be overridden. Again, this
model may be modified by a lazy consensus declaration when the request for
a vote is raised, but the full-stop nature of a negative vote is unchanged.
Under normal (non-lazy consensus) conditions, the proposal requires three
positive votes and no negative ones in order to pass; if it fails to garner
the requisite amount of support, it doesn't -- and typically is either
withdrawn, modified, or simply allowed to languish as an open issue until
someone gets around to removing it.
---
As @cos mentioned earlier in the thread, the vote is on the bigtop code
base and (to me) falls under the above code modification guidelines. He
found a blocking RAT issue with the bigtop source and voted -1. There is
no math that can dilute his veto.
I'm far from an expert on ASF voting, but that's my read on why a binding
-1 could block the release.
-Kevin
On Thu, Oct 19, 2017 at 3:29 PM, Arnaud Launay <as...@launay.org> wrote:
> Le Fri, Oct 20, 2017 at 01:20:18AM +0800, Evans Ye a écrit:
> > To summarize the vote result:
> > The vote is REJECTED with 3 binding +1s, 1 binding -1 and 1 non-binding
> -1.
>
> Just out of curiosity: 1 binding -1 is sufficient to derail the
> vote ?
>
> Because to me, if you say something like "binding counts twice",
> it goes :
>
> 3*(1*2)+1*(-1*2)+1*(1*-1)
> 3
>
> Even with basic voting:
> 3-1-1
> 1
>
> Still positive ? :)
>
>
> Arnaud.
>
Re: [VOTE] Release Bigtop version 1.2.1
Posted by Arnaud Launay <as...@launay.org>.
Le Fri, Oct 20, 2017 at 01:20:18AM +0800, Evans Ye a écrit:
> To summarize the vote result:
> The vote is REJECTED with 3 binding +1s, 1 binding -1 and 1 non-binding -1.
Just out of curiosity: 1 binding -1 is sufficient to derail the
vote ?
Because to me, if you say something like "binding counts twice",
it goes :
3*(1*2)+1*(-1*2)+1*(1*-1)
3
Even with basic voting:
3-1-1
1
Still positive ? :)
Arnaud.
Re: [VOTE] Release Bigtop version 1.2.1
Posted by Evans Ye <ev...@apache.org>.
OK. I think if we can't get it fixed soon, we can still explain how to
evaluate our release on the download page. BIGTOP-2892
<https://issues.apache.org/jira/browse/BIGTOP-2892> is opened for this.
To summarize the vote result:
The vote is REJECTED with 3 binding +1s, 1 binding -1 and 1 non-binding -1.
Thanks for voting!
2017-10-20 0:05 GMT+08:00 Konstantin Boudnik <co...@apache.org>:
> Yes, the checksum matches the file - no problem with that. However,
> sha1sum (and all other SHA's for that matter) look like this
> % sha1sum /etc/passwd
> f36e0ac05f911c031660a8737628d4f0595af2c4 /etc/passwd
>
> When you later run
>
> % sha1sum /etc/passwd.sha1
> is will validate the file automatically. The checksum in the 1.2.1
> only includes the hash, so the validation needs to be done manually.
>
> Looks like we were producing the sums like that before (likely the
> maven thing), so it isn't specific to 1.2.1. I will open a bug (unless
> one exists to fix the situation).
>
> Thanks!
> --
> With regards,
> Konstantin (Cos) Boudnik
> 2CAC 8312 4870 D885 8616 6115 220F 6980 1F27 E622
>
> Disclaimer: Opinions expressed in this email are those of the author,
> and do not necessarily represent the views of any company the author
> might be affiliated with at the moment of writing.
>
>
> On Thu, Oct 19, 2017 at 8:43 AM, Evans Ye <ev...@apache.org> wrote:
> > 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 <co...@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 <co...@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 <ev...@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
> >> > > > >
> >> > >
> >>
>
Re: [VOTE] Release Bigtop version 1.2.1
Posted by Konstantin Boudnik <co...@apache.org>.
Yes, the checksum matches the file - no problem with that. However,
sha1sum (and all other SHA's for that matter) look like this
% sha1sum /etc/passwd
f36e0ac05f911c031660a8737628d4f0595af2c4 /etc/passwd
When you later run
% sha1sum /etc/passwd.sha1
is will validate the file automatically. The checksum in the 1.2.1
only includes the hash, so the validation needs to be done manually.
Looks like we were producing the sums like that before (likely the
maven thing), so it isn't specific to 1.2.1. I will open a bug (unless
one exists to fix the situation).
Thanks!
--
With regards,
Konstantin (Cos) Boudnik
2CAC 8312 4870 D885 8616 6115 220F 6980 1F27 E622
Disclaimer: Opinions expressed in this email are those of the author,
and do not necessarily represent the views of any company the author
might be affiliated with at the moment of writing.
On Thu, Oct 19, 2017 at 8:43 AM, Evans Ye <ev...@apache.org> wrote:
> 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 <co...@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 <co...@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 <ev...@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
>> > > > >
>> > >
>>
Re: [VOTE] Release Bigtop version 1.2.1
Posted by Evans Ye <ev...@apache.org>.
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 <co...@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 <co...@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 <ev...@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
> > > > >
> > >
>
Re: [VOTE] Release Bigtop version 1.2.1
Posted by Konstantin Boudnik <co...@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 <co...@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 <ev...@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
> > > >
> >
Re: [VOTE] Release Bigtop version 1.2.1
Posted by Kevin Monroe <ke...@canonical.com>.
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 <co...@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 <ev...@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
> > >
>
Re: [VOTE] Release Bigtop version 1.2.1
Posted by Konstantin Boudnik <co...@apache.org>.
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 <ev...@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
> >
Re: [VOTE] Release Bigtop version 1.2.1
Posted by Kevin Monroe <ke...@canonical.com>.
-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 <ev...@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
>
Re: [VOTE] Release Bigtop version 1.2.1
Posted by Kevin Monroe <ke...@canonical.com>.
I've opened the following to get the giraph-examples.jar binary out of the
source tree:
https://issues.apache.org/jira/browse/BIGTOP-2908
Thanks,
-Kevin
On Wed, Oct 18, 2017 at 2:47 PM, Konstantin Boudnik <co...@apache.org> wrote:
> -1 [binding]
>
> Verified:
> - signature (passed)
> - sha1 (the file is malformed, which makes sha1sum -c impossible) (passed)
> - RAT (failed)
> The release tarball includes a binary file [1]. If the file is definetely
> should be a part of the release (which I have my reservations as this
> goes
> against source-only policy of the ASF), then at the very least we need to
> add it into RAT exclue list.
>
> [1] bigtop-packages/src/charm/giraph/layer-giraph/resources/
> giraph-examples-1.1.0.jar
>
> Thank you!
> Cos
>
> On Fri, Oct 13, 2017 at 02:30AM, Evans Ye 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
>
Re: [VOTE] Release Bigtop version 1.2.1
Posted by Konstantin Boudnik <co...@apache.org>.
-1 [binding]
Verified:
- signature (passed)
- sha1 (the file is malformed, which makes sha1sum -c impossible) (passed)
- RAT (failed)
The release tarball includes a binary file [1]. If the file is definetely
should be a part of the release (which I have my reservations as this goes
against source-only policy of the ASF), then at the very least we need to
add it into RAT exclue list.
[1] bigtop-packages/src/charm/giraph/layer-giraph/resources/giraph-examples-1.1.0.jar
Thank you!
Cos
On Fri, Oct 13, 2017 at 02:30AM, Evans Ye 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