You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@accumulo.apache.org by Josh Elser <el...@apache.org> on 2015/09/05 23:27:37 UTC
[VOTE] Accumulo 1.5.4-rc1
Accumulo Developers,
Please consider the following candidate for Accumulo 1.5.4.
Git Commit:
12a1041dcbb7f3b10543c305f27ece4b0d65ab9c
Branch:
1.5.4-rc1
If this vote passes, a gpg-signed tag will be created using:
git tag -f -m 'Apache Accumulo 1.5.4' -s 1.5.4
12a1041dcbb7f3b10543c305f27ece4b0d65ab9c
Staging repo:
https://repository.apache.org/content/repositories/orgapacheaccumulo-1039
Source (official release artifact):
https://repository.apache.org/content/repositories/orgapacheaccumulo-1039/org/apache/accumulo/accumulo/1.5.4/accumulo-1.5.4-src.tar.gz
Binary:
https://repository.apache.org/content/repositories/orgapacheaccumulo-1039/org/apache/accumulo/accumulo/1.5.4/accumulo-1.5.4-bin.tar.gz
(Append ".sha1", ".md5", or ".asc" to download the signature/hash for a
given artifact.)
All artifacts were built and staged with:
mvn release:prepare && mvn release:perform
Signing keys are available at https://www.apache.org/dist/accumulo/KEYS
(Expected fingerprint: ABC8914C675FAD3FA74F39B2D146D62CAB471AE9)
Release notes (in progress) can be found at
https://accumulo.apache.org/release_notes/1.5.4
Please vote one of:
[ ] +1 - I have verified and accept...
[ ] +0 - I have reservations, but not strong enough to vote against...
[ ] -1 - Because..., I do not accept...
... these artifacts as the 1.5.4 release of Apache Accumulo.
This vote will end on Thurs Sep 10 23:00:00 UTC 2015
(Thurs Sep 10 20:00:00 EDT 2015 / Thurs Sep 10 17:00:00 PDT 2015)
Thanks!
P.S. Hint: download the whole staging repo with
wget -erobots=off -r -l inf -np -nH \
https://repository.apache.org/content/repositories/orgapacheaccumulo-1039/
# note the trailing slash is needed
Re: [VOTE] Accumulo 1.5.4-rc1
Posted by Eric Newton <er...@gmail.com>.
+1
Verified signatures, built, ran unit tests, started everything up and
performed (limited) tests.
Thanks Josh!
-Eric
On Tue, Sep 8, 2015 at 2:39 PM, Josh Elser <el...@apache.org> wrote:
> Also, a heads-up since I had one question about this already: you
> (hopefully) will notice that this was signed using a different key than
> previously for me. This is expected.
>
> I built this release on a virtual server (under my virtual but not
> physical control). As such, I did not feel comfortable placing my existing
> private key on this server and created a new one instead.
>
> You'll want to recv-keys on my new key when verifying checksums: `gpg
> --keyserver pgp.mit.edu --recv-keys AB471AE9`
>
>
> Josh Elser wrote:
>
>> Accumulo Developers,
>>
>> Please consider the following candidate for Accumulo 1.5.4.
>>
>> Git Commit:
>> 12a1041dcbb7f3b10543c305f27ece4b0d65ab9c
>> Branch:
>> 1.5.4-rc1
>>
>> If this vote passes, a gpg-signed tag will be created using:
>> git tag -f -m 'Apache Accumulo 1.5.4' -s 1.5.4
>> 12a1041dcbb7f3b10543c305f27ece4b0d65ab9c
>>
>> Staging repo:
>> https://repository.apache.org/content/repositories/orgapacheaccumulo-1039
>> Source (official release artifact):
>>
>> https://repository.apache.org/content/repositories/orgapacheaccumulo-1039/org/apache/accumulo/accumulo/1.5.4/accumulo-1.5.4-src.tar.gz
>>
>> Binary:
>>
>> https://repository.apache.org/content/repositories/orgapacheaccumulo-1039/org/apache/accumulo/accumulo/1.5.4/accumulo-1.5.4-bin.tar.gz
>>
>> (Append ".sha1", ".md5", or ".asc" to download the signature/hash for a
>> given artifact.)
>>
>> All artifacts were built and staged with:
>> mvn release:prepare && mvn release:perform
>>
>> Signing keys are available at https://www.apache.org/dist/accumulo/KEYS
>> (Expected fingerprint: ABC8914C675FAD3FA74F39B2D146D62CAB471AE9)
>>
>> Release notes (in progress) can be found at
>> https://accumulo.apache.org/release_notes/1.5.4
>>
>> Please vote one of:
>> [ ] +1 - I have verified and accept...
>> [ ] +0 - I have reservations, but not strong enough to vote against...
>> [ ] -1 - Because..., I do not accept...
>> ... these artifacts as the 1.5.4 release of Apache Accumulo.
>>
>> This vote will end on Thurs Sep 10 23:00:00 UTC 2015
>> (Thurs Sep 10 20:00:00 EDT 2015 / Thurs Sep 10 17:00:00 PDT 2015)
>>
>> Thanks!
>>
>> P.S. Hint: download the whole staging repo with
>> wget -erobots=off -r -l inf -np -nH \
>>
>> https://repository.apache.org/content/repositories/orgapacheaccumulo-1039/
>> # note the trailing slash is needed
>>
>
Re: [VOTE] Accumulo 1.5.4-rc1
Posted by Josh Elser <el...@apache.org>.
Also, a heads-up since I had one question about this already: you
(hopefully) will notice that this was signed using a different key than
previously for me. This is expected.
I built this release on a virtual server (under my virtual but not
physical control). As such, I did not feel comfortable placing my
existing private key on this server and created a new one instead.
You'll want to recv-keys on my new key when verifying checksums: `gpg
--keyserver pgp.mit.edu --recv-keys AB471AE9`
Josh Elser wrote:
> Accumulo Developers,
>
> Please consider the following candidate for Accumulo 1.5.4.
>
> Git Commit:
> 12a1041dcbb7f3b10543c305f27ece4b0d65ab9c
> Branch:
> 1.5.4-rc1
>
> If this vote passes, a gpg-signed tag will be created using:
> git tag -f -m 'Apache Accumulo 1.5.4' -s 1.5.4
> 12a1041dcbb7f3b10543c305f27ece4b0d65ab9c
>
> Staging repo:
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1039
> Source (official release artifact):
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1039/org/apache/accumulo/accumulo/1.5.4/accumulo-1.5.4-src.tar.gz
>
> Binary:
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1039/org/apache/accumulo/accumulo/1.5.4/accumulo-1.5.4-bin.tar.gz
>
> (Append ".sha1", ".md5", or ".asc" to download the signature/hash for a
> given artifact.)
>
> All artifacts were built and staged with:
> mvn release:prepare && mvn release:perform
>
> Signing keys are available at https://www.apache.org/dist/accumulo/KEYS
> (Expected fingerprint: ABC8914C675FAD3FA74F39B2D146D62CAB471AE9)
>
> Release notes (in progress) can be found at
> https://accumulo.apache.org/release_notes/1.5.4
>
> Please vote one of:
> [ ] +1 - I have verified and accept...
> [ ] +0 - I have reservations, but not strong enough to vote against...
> [ ] -1 - Because..., I do not accept...
> ... these artifacts as the 1.5.4 release of Apache Accumulo.
>
> This vote will end on Thurs Sep 10 23:00:00 UTC 2015
> (Thurs Sep 10 20:00:00 EDT 2015 / Thurs Sep 10 17:00:00 PDT 2015)
>
> Thanks!
>
> P.S. Hint: download the whole staging repo with
> wget -erobots=off -r -l inf -np -nH \
>
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1039/
> # note the trailing slash is needed
Re: [VOTE] Accumulo 1.5.4-rc1
Posted by Billie Rinaldi <bi...@apache.org>.
+1
test/src/test/java/org/apache/accumulo/test/DeleteRowsTest.java has a
botched license header, but I wouldn't consider that a blocker since most
of it is intact. Otherwise the licenses look good, the tarball contents
look good, and the source tarball matches the git branch. I verified the
checksums and signatures, built from source and ran mvn verify.
On Sat, Sep 5, 2015 at 2:27 PM, Josh Elser <el...@apache.org> wrote:
> Accumulo Developers,
>
> Please consider the following candidate for Accumulo 1.5.4.
>
> Git Commit:
> 12a1041dcbb7f3b10543c305f27ece4b0d65ab9c
> Branch:
> 1.5.4-rc1
>
> If this vote passes, a gpg-signed tag will be created using:
> git tag -f -m 'Apache Accumulo 1.5.4' -s 1.5.4
> 12a1041dcbb7f3b10543c305f27ece4b0d65ab9c
>
> Staging repo:
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1039
> Source (official release artifact):
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1039/org/apache/accumulo/accumulo/1.5.4/accumulo-1.5.4-src.tar.gz
> Binary:
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1039/org/apache/accumulo/accumulo/1.5.4/accumulo-1.5.4-bin.tar.gz
> (Append ".sha1", ".md5", or ".asc" to download the signature/hash for a
> given artifact.)
>
> All artifacts were built and staged with:
> mvn release:prepare && mvn release:perform
>
> Signing keys are available at https://www.apache.org/dist/accumulo/KEYS
> (Expected fingerprint: ABC8914C675FAD3FA74F39B2D146D62CAB471AE9)
>
> Release notes (in progress) can be found at
> https://accumulo.apache.org/release_notes/1.5.4
>
> Please vote one of:
> [ ] +1 - I have verified and accept...
> [ ] +0 - I have reservations, but not strong enough to vote against...
> [ ] -1 - Because..., I do not accept...
> ... these artifacts as the 1.5.4 release of Apache Accumulo.
>
> This vote will end on Thurs Sep 10 23:00:00 UTC 2015
> (Thurs Sep 10 20:00:00 EDT 2015 / Thurs Sep 10 17:00:00 PDT 2015)
>
> Thanks!
>
> P.S. Hint: download the whole staging repo with
> wget -erobots=off -r -l inf -np -nH \
>
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1039/
> # note the trailing slash is needed
>
Re: [VOTE] Accumulo 1.5.4-rc1
Posted by Josh Elser <jo...@gmail.com>.
Sean Busbey wrote:
>> > So let's deal with the matter of the vote at hand first. After that we can
>>> >> deal with fixing things, hopefully with Josh abstaining. (Josh I'd
>>> >> recommend un-assigning yourself from the issue if you'd prefer someone
>>> >> else
>>> >> take it up.)
>>> >>
>>> >>
>> > I'll likely make time tonight to bash through as many of the issues as I
>> > can tonight. The assumption was that if 1.5.4 was going to happen "now", I
>> > would be the one who had to do it, hence my quick self-assign. Hopefully
>> > that was not interpreted as I'm doing it all (I think not since Christopher
>> > had asked me how he could help too).
>> >
>> > I'm not sure why I have to abstain... but I think I've already said my
>> > peace on the matter. Eric has told me in confidence (that I'm apparently
>> > going to violate) that he has drafted a number of responses already, but
>> > hasn't sent them due to being frustrated.
>> >
>> >
> I still feel weird taking on work that someone else is actively working on.
> But making a subtask as Christopher has done works well for me.
I see you've already moved forward. You have my blessing (again). I will
catch up tonight with progress as defined.
Re: [VOTE] Accumulo 1.5.4-rc1
Posted by Sean Busbey <bu...@cloudera.com>.
On Thu, Sep 10, 2015 at 5:49 PM, Josh Elser <jo...@gmail.com> wrote:
>
>
> Sean Busbey wrote:
>
>>
>>
> So let's deal with the matter of the vote at hand first. After that we can
>> deal with fixing things, hopefully with Josh abstaining. (Josh I'd
>> recommend un-assigning yourself from the issue if you'd prefer someone
>> else
>> take it up.)
>>
>>
> I'll likely make time tonight to bash through as many of the issues as I
> can tonight. The assumption was that if 1.5.4 was going to happen "now", I
> would be the one who had to do it, hence my quick self-assign. Hopefully
> that was not interpreted as I'm doing it all (I think not since Christopher
> had asked me how he could help too).
>
> I'm not sure why I have to abstain... but I think I've already said my
> peace on the matter. Eric has told me in confidence (that I'm apparently
> going to violate) that he has drafted a number of responses already, but
> hasn't sent them due to being frustrated.
>
>
I still feel weird taking on work that someone else is actively working on.
But making a subtask as Christopher has done works well for me.
> At risk of suggesting that we vote on a vote.. what do you think needs to
> happen now?
>
Personally I'd like to see a quick fix of the issues (they are much quicker
fixes then I've seen in other communities) and a new RC go out.
--
Sean
Re: [VOTE] Accumulo 1.5.4-rc1
Posted by Josh Elser <jo...@gmail.com>.
Sean Busbey wrote:
> We can't tie the ability to vote -1 on a release to volunteering to fix the
> issue that causes a -1. Presuming a release is valued by the community, the
> work will get done.
>
> At the same time, it is crappy for Josh to be expected to fix everything,
> especially if he doesn't want to fill the role of janitor. We all have
> plenty of other things to do, but so does he.
Thanks.
> So let's deal with the matter of the vote at hand first. After that we can
> deal with fixing things, hopefully with Josh abstaining. (Josh I'd
> recommend un-assigning yourself from the issue if you'd prefer someone else
> take it up.)
>
I'll likely make time tonight to bash through as many of the issues as I
can tonight. The assumption was that if 1.5.4 was going to happen "now",
I would be the one who had to do it, hence my quick self-assign.
Hopefully that was not interpreted as I'm doing it all (I think not
since Christopher had asked me how he could help too).
I'm not sure why I have to abstain... but I think I've already said my
peace on the matter. Eric has told me in confidence (that I'm apparently
going to violate) that he has drafted a number of responses already, but
hasn't sent them due to being frustrated.
At risk of suggesting that we vote on a vote.. what do you think needs
to happen now?
Re: [VOTE] Accumulo 1.5.4-rc1
Posted by Sean Busbey <bu...@cloudera.com>.
We can't tie the ability to vote -1 on a release to volunteering to fix the
issue that causes a -1. Presuming a release is valued by the community, the
work will get done.
At the same time, it is crappy for Josh to be expected to fix everything,
especially if he doesn't want to fill the role of janitor. We all have
plenty of other things to do, but so does he.
So let's deal with the matter of the vote at hand first. After that we can
deal with fixing things, hopefully with Josh abstaining. (Josh I'd
recommend un-assigning yourself from the issue if you'd prefer someone else
take it up.)
--
Sean
On Sep 10, 2015 3:19 PM, "Josh Elser" <el...@apache.org> wrote:
> Christopher wrote:
>
>> The larger concern I have is that expecting it to be fixed prior to 1.5.4
>> might mean loss of willingness to create an RC2 for 1.5.4 and release it
>> at
>> all. Recall, the 1.5 branch was only revived at all to fix some critical
>> issues and move on. It's still a viable alternative to abandon 1.5.x and
>> focus on fixing these issues in 1.6, and later, where we've made dramatic
>> improvements to the build. Fixing these newly identified issues is going
>> to
>> take some time and effort. It's not that it can't be done for 1.5.4... but
>> the question is... who is going to do it? Is anybody who issued a "-1"
>> willing to step up and resolve these issues? Or will it rely on Josh? I'm
>> currently looking at some of the issues to try to help out if I can, but I
>> also have other obligations.
>>
>>
> Thanks for consideration, Christopher.
>
> While people sharing their opinion is appreciated, a repeated reaction
> without offered effort put behind it can come across in bad taste. Not
> trying to do discourage the conversation I asked for, I just would love to
> come back and see a patch to _fix_ one of the many nits outlined instead of
> another "me too".
>
Re: [VOTE] Accumulo 1.5.4-rc1
Posted by Josh Elser <el...@apache.org>.
Christopher wrote:
> The larger concern I have is that expecting it to be fixed prior to 1.5.4
> might mean loss of willingness to create an RC2 for 1.5.4 and release it at
> all. Recall, the 1.5 branch was only revived at all to fix some critical
> issues and move on. It's still a viable alternative to abandon 1.5.x and
> focus on fixing these issues in 1.6, and later, where we've made dramatic
> improvements to the build. Fixing these newly identified issues is going to
> take some time and effort. It's not that it can't be done for 1.5.4... but
> the question is... who is going to do it? Is anybody who issued a "-1"
> willing to step up and resolve these issues? Or will it rely on Josh? I'm
> currently looking at some of the issues to try to help out if I can, but I
> also have other obligations.
>
Thanks for consideration, Christopher.
While people sharing their opinion is appreciated, a repeated reaction
without offered effort put behind it can come across in bad taste. Not
trying to do discourage the conversation I asked for, I just would love
to come back and see a patch to _fix_ one of the many nits outlined
instead of another "me too".
Re: [VOTE] Accumulo 1.5.4-rc1
Posted by Josh Elser <jo...@gmail.com>.
I _think_ we put ourselves in hot-water too if that becomes a norm, but
I understand the point. I just saw that as a assumption a user could do.
Specifically, the user who asked for this release, James, had asked for
a release which is why I was confused at your comment.
dlmarion@comcast.net wrote:
> Not suggesting encouragement to use the release. But if someone is stuck on 1.5, and needs the fix, there is an alternative. I speak from experience on this issue w/r/t a different Apache project.
>
>> -----Original Message-----
>> From: Christopher [mailto:ctubbsii@apache.org]
>> Sent: Thursday, September 10, 2015 5:30 PM
>> To: dev@accumulo.apache.org
>> Subject: Re: [VOTE] Accumulo 1.5.4-rc1
>>
>> Not releasing is a viable option, but we can't encourage users to use an
>> unreleased version of our code. That's not an appropriate substitute for
>> releasing.
>>
>> On Thu, Sep 10, 2015 at 4:19 PM<dl...@comcast.net> wrote:
>>
>>> If the critical issues are fixed in 1.5.x, and someone needs them,
>>> can't they check out the source and build it themselves? Is that a viable
>> option?
>>> ----- Original Message -----
>>>
>>> From: "Christopher"<ct...@apache.org>
>>> To: dev@accumulo.apache.org
>>> Sent: Thursday, September 10, 2015 3:44:20 PM
>>> Subject: Re: [VOTE] Accumulo 1.5.4-rc1
>>>
>>> The larger concern I have is that expecting it to be fixed prior to
>>> 1.5.4 might mean loss of willingness to create an RC2 for 1.5.4 and
>>> release it at all. Recall, the 1.5 branch was only revived at all to
>>> fix some critical issues and move on. It's still a viable alternative
>>> to abandon 1.5.x and focus on fixing these issues in 1.6, and later,
>>> where we've made dramatic improvements to the build. Fixing these
>>> newly identified issues is going to take some time and effort. It's
>>> not that it can't be done for 1.5.4... but the question is... who is going to do
>> it? Is anybody who issued a "-1"
>>> willing to step up and resolve these issues? Or will it rely on Josh?
>>> I'm currently looking at some of the issues to try to help out if I
>>> can, but I also have other obligations.
>>>
>>> On Thu, Sep 10, 2015 at 3:33 PM Alex Moundalexis<al...@cloudera.com>
>>> wrote:
>>>
>>>> -1 (non-binding)
>>>>
>>>> Fix now and it'll be fixed here and in 1.6.x.
>>>>
>>>> On Thu, Sep 10, 2015 at 2:46 AM, Sean Busbey<bu...@cloudera.com>
>>> wrote:
>>>>> -1
>>>>>
>>>>> * signatures check out
>>>>> * checksums match
>>>>> * licensing errors noted in ACCUMULO-3988
>>>>>
>>>>> On Sat, Sep 5, 2015 at 4:27 PM, Josh Elser<el...@apache.org> wrote:
>>>>>
>>>>>> Accumulo Developers,
>>>>>>
>>>>>> Please consider the following candidate for Accumulo 1.5.4.
>>>>>>
>>>>>> Git Commit:
>>>>>> 12a1041dcbb7f3b10543c305f27ece4b0d65ab9c
>>>>>> Branch:
>>>>>> 1.5.4-rc1
>>>>>>
>>>>>> If this vote passes, a gpg-signed tag will be created using:
>>>>>> git tag -f -m 'Apache Accumulo 1.5.4' -s 1.5.4
>>>>>> 12a1041dcbb7f3b10543c305f27ece4b0d65ab9c
>>>>>>
>>>>>> Staging repo:
>>>>>>
>>> https://repository.apache.org/content/repositories/orgapacheaccumulo-1
>>> 039
>>>>>> Source (official release artifact):
>>>>>>
>>> https://repository.apache.org/content/repositories/orgapacheaccumulo-1
>>> 039/org/apache/accumulo/accumulo/1.5.4/accumulo-1.5.4-src.tar.gz
>>>>>> Binary:
>>>>>>
>>> https://repository.apache.org/content/repositories/orgapacheaccumulo-1
>>> 039/org/apache/accumulo/accumulo/1.5.4/accumulo-1.5.4-bin.tar.gz
>>>>>> (Append ".sha1", ".md5", or ".asc" to download the
>>>>>> signature/hash
>>> for a
>>>>>> given artifact.)
>>>>>>
>>>>>> All artifacts were built and staged with:
>>>>>> mvn release:prepare&& mvn release:perform
>>>>>>
>>>>>> Signing keys are available at
>>>> https://www.apache.org/dist/accumulo/KEYS
>>>>>> (Expected fingerprint:
>> ABC8914C675FAD3FA74F39B2D146D62CAB471AE9)
>>>>>> Release notes (in progress) can be found at
>>>>>> https://accumulo.apache.org/release_notes/1.5.4
>>>>>>
>>>>>> Please vote one of:
>>>>>> [ ] +1 - I have verified and accept...
>>>>>> [ ] +0 - I have reservations, but not strong enough to vote
>>> against...
>>>>>> [ ] -1 - Because..., I do not accept...
>>>>>> ... these artifacts as the 1.5.4 release of Apache Accumulo.
>>>>>>
>>>>>> This vote will end on Thurs Sep 10 23:00:00 UTC 2015 (Thurs Sep
>>>>>> 10 20:00:00 EDT 2015 / Thurs Sep 10 17:00:00 PDT 2015)
>>>>>>
>>>>>> Thanks!
>>>>>>
>>>>>> P.S. Hint: download the whole staging repo with wget
>>>>>> -erobots=off -r -l inf -np -nH \
>>>>>>
>>>>>>
>>> https://repository.apache.org/content/repositories/orgapacheaccumulo-1
>>> 039/
>>>>>> # note the trailing slash is needed
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Sean
>>>>>
>>>
>
RE: [VOTE] Accumulo 1.5.4-rc1
Posted by dl...@comcast.net.
Not suggesting encouragement to use the release. But if someone is stuck on 1.5, and needs the fix, there is an alternative. I speak from experience on this issue w/r/t a different Apache project.
> -----Original Message-----
> From: Christopher [mailto:ctubbsii@apache.org]
> Sent: Thursday, September 10, 2015 5:30 PM
> To: dev@accumulo.apache.org
> Subject: Re: [VOTE] Accumulo 1.5.4-rc1
>
> Not releasing is a viable option, but we can't encourage users to use an
> unreleased version of our code. That's not an appropriate substitute for
> releasing.
>
> On Thu, Sep 10, 2015 at 4:19 PM <dl...@comcast.net> wrote:
>
> >
> > If the critical issues are fixed in 1.5.x, and someone needs them,
> > can't they check out the source and build it themselves? Is that a viable
> option?
> >
> > ----- Original Message -----
> >
> > From: "Christopher" <ct...@apache.org>
> > To: dev@accumulo.apache.org
> > Sent: Thursday, September 10, 2015 3:44:20 PM
> > Subject: Re: [VOTE] Accumulo 1.5.4-rc1
> >
> > The larger concern I have is that expecting it to be fixed prior to
> > 1.5.4 might mean loss of willingness to create an RC2 for 1.5.4 and
> > release it at all. Recall, the 1.5 branch was only revived at all to
> > fix some critical issues and move on. It's still a viable alternative
> > to abandon 1.5.x and focus on fixing these issues in 1.6, and later,
> > where we've made dramatic improvements to the build. Fixing these
> > newly identified issues is going to take some time and effort. It's
> > not that it can't be done for 1.5.4... but the question is... who is going to do
> it? Is anybody who issued a "-1"
> > willing to step up and resolve these issues? Or will it rely on Josh?
> > I'm currently looking at some of the issues to try to help out if I
> > can, but I also have other obligations.
> >
> > On Thu, Sep 10, 2015 at 3:33 PM Alex Moundalexis <al...@cloudera.com>
> > wrote:
> >
> > > -1 (non-binding)
> > >
> > > Fix now and it'll be fixed here and in 1.6.x.
> > >
> > > On Thu, Sep 10, 2015 at 2:46 AM, Sean Busbey <bu...@cloudera.com>
> > wrote:
> > >
> > > > -1
> > > >
> > > > * signatures check out
> > > > * checksums match
> > > > * licensing errors noted in ACCUMULO-3988
> > > >
> > > > On Sat, Sep 5, 2015 at 4:27 PM, Josh Elser <el...@apache.org> wrote:
> > > >
> > > > > Accumulo Developers,
> > > > >
> > > > > Please consider the following candidate for Accumulo 1.5.4.
> > > > >
> > > > > Git Commit:
> > > > > 12a1041dcbb7f3b10543c305f27ece4b0d65ab9c
> > > > > Branch:
> > > > > 1.5.4-rc1
> > > > >
> > > > > If this vote passes, a gpg-signed tag will be created using:
> > > > > git tag -f -m 'Apache Accumulo 1.5.4' -s 1.5.4
> > > > > 12a1041dcbb7f3b10543c305f27ece4b0d65ab9c
> > > > >
> > > > > Staging repo:
> > > > >
> > > >
> > >
> > https://repository.apache.org/content/repositories/orgapacheaccumulo-1
> > 039
> > > > > Source (official release artifact):
> > > > >
> > > >
> > >
> > https://repository.apache.org/content/repositories/orgapacheaccumulo-1
> > 039/org/apache/accumulo/accumulo/1.5.4/accumulo-1.5.4-src.tar.gz
> > > > > Binary:
> > > > >
> > > >
> > >
> > https://repository.apache.org/content/repositories/orgapacheaccumulo-1
> > 039/org/apache/accumulo/accumulo/1.5.4/accumulo-1.5.4-bin.tar.gz
> > > > > (Append ".sha1", ".md5", or ".asc" to download the
> > > > > signature/hash
> > for a
> > > > > given artifact.)
> > > > >
> > > > > All artifacts were built and staged with:
> > > > > mvn release:prepare && mvn release:perform
> > > > >
> > > > > Signing keys are available at
> > > https://www.apache.org/dist/accumulo/KEYS
> > > > > (Expected fingerprint:
> ABC8914C675FAD3FA74F39B2D146D62CAB471AE9)
> > > > >
> > > > > Release notes (in progress) can be found at
> > > > > https://accumulo.apache.org/release_notes/1.5.4
> > > > >
> > > > > Please vote one of:
> > > > > [ ] +1 - I have verified and accept...
> > > > > [ ] +0 - I have reservations, but not strong enough to vote
> > against...
> > > > > [ ] -1 - Because..., I do not accept...
> > > > > ... these artifacts as the 1.5.4 release of Apache Accumulo.
> > > > >
> > > > > This vote will end on Thurs Sep 10 23:00:00 UTC 2015 (Thurs Sep
> > > > > 10 20:00:00 EDT 2015 / Thurs Sep 10 17:00:00 PDT 2015)
> > > > >
> > > > > Thanks!
> > > > >
> > > > > P.S. Hint: download the whole staging repo with wget
> > > > > -erobots=off -r -l inf -np -nH \
> > > > >
> > > > >
> > > >
> > >
> > https://repository.apache.org/content/repositories/orgapacheaccumulo-1
> > 039/
> > > > > # note the trailing slash is needed
> > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Sean
> > > >
> > >
> >
> >
Re: [VOTE] Accumulo 1.5.4-rc1
Posted by Christopher <ct...@apache.org>.
Not releasing is a viable option, but we can't encourage users to use an
unreleased version of our code. That's not an appropriate substitute for
releasing.
On Thu, Sep 10, 2015 at 4:19 PM <dl...@comcast.net> wrote:
>
> If the critical issues are fixed in 1.5.x, and someone needs them, can't
> they check out the source and build it themselves? Is that a viable option?
>
> ----- Original Message -----
>
> From: "Christopher" <ct...@apache.org>
> To: dev@accumulo.apache.org
> Sent: Thursday, September 10, 2015 3:44:20 PM
> Subject: Re: [VOTE] Accumulo 1.5.4-rc1
>
> The larger concern I have is that expecting it to be fixed prior to 1.5.4
> might mean loss of willingness to create an RC2 for 1.5.4 and release it at
> all. Recall, the 1.5 branch was only revived at all to fix some critical
> issues and move on. It's still a viable alternative to abandon 1.5.x and
> focus on fixing these issues in 1.6, and later, where we've made dramatic
> improvements to the build. Fixing these newly identified issues is going to
> take some time and effort. It's not that it can't be done for 1.5.4... but
> the question is... who is going to do it? Is anybody who issued a "-1"
> willing to step up and resolve these issues? Or will it rely on Josh? I'm
> currently looking at some of the issues to try to help out if I can, but I
> also have other obligations.
>
> On Thu, Sep 10, 2015 at 3:33 PM Alex Moundalexis <al...@cloudera.com>
> wrote:
>
> > -1 (non-binding)
> >
> > Fix now and it'll be fixed here and in 1.6.x.
> >
> > On Thu, Sep 10, 2015 at 2:46 AM, Sean Busbey <bu...@cloudera.com>
> wrote:
> >
> > > -1
> > >
> > > * signatures check out
> > > * checksums match
> > > * licensing errors noted in ACCUMULO-3988
> > >
> > > On Sat, Sep 5, 2015 at 4:27 PM, Josh Elser <el...@apache.org> wrote:
> > >
> > > > Accumulo Developers,
> > > >
> > > > Please consider the following candidate for Accumulo 1.5.4.
> > > >
> > > > Git Commit:
> > > > 12a1041dcbb7f3b10543c305f27ece4b0d65ab9c
> > > > Branch:
> > > > 1.5.4-rc1
> > > >
> > > > If this vote passes, a gpg-signed tag will be created using:
> > > > git tag -f -m 'Apache Accumulo 1.5.4' -s 1.5.4
> > > > 12a1041dcbb7f3b10543c305f27ece4b0d65ab9c
> > > >
> > > > Staging repo:
> > > >
> > >
> >
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1039
> > > > Source (official release artifact):
> > > >
> > >
> >
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1039/org/apache/accumulo/accumulo/1.5.4/accumulo-1.5.4-src.tar.gz
> > > > Binary:
> > > >
> > >
> >
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1039/org/apache/accumulo/accumulo/1.5.4/accumulo-1.5.4-bin.tar.gz
> > > > (Append ".sha1", ".md5", or ".asc" to download the signature/hash
> for a
> > > > given artifact.)
> > > >
> > > > All artifacts were built and staged with:
> > > > mvn release:prepare && mvn release:perform
> > > >
> > > > Signing keys are available at
> > https://www.apache.org/dist/accumulo/KEYS
> > > > (Expected fingerprint: ABC8914C675FAD3FA74F39B2D146D62CAB471AE9)
> > > >
> > > > Release notes (in progress) can be found at
> > > > https://accumulo.apache.org/release_notes/1.5.4
> > > >
> > > > Please vote one of:
> > > > [ ] +1 - I have verified and accept...
> > > > [ ] +0 - I have reservations, but not strong enough to vote
> against...
> > > > [ ] -1 - Because..., I do not accept...
> > > > ... these artifacts as the 1.5.4 release of Apache Accumulo.
> > > >
> > > > This vote will end on Thurs Sep 10 23:00:00 UTC 2015
> > > > (Thurs Sep 10 20:00:00 EDT 2015 / Thurs Sep 10 17:00:00 PDT 2015)
> > > >
> > > > Thanks!
> > > >
> > > > P.S. Hint: download the whole staging repo with
> > > > wget -erobots=off -r -l inf -np -nH \
> > > >
> > > >
> > >
> >
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1039/
> > > > # note the trailing slash is needed
> > > >
> > >
> > >
> > >
> > > --
> > > Sean
> > >
> >
>
>
RE: [VOTE] Accumulo 1.5.4-rc1
Posted by dl...@comcast.net.
I'm just looking for a way to resolve this given that we have a bunch of -1 votes and no volunteers to fix the issue. Your work is not lost if there is no release. In fact, based on what I read regarding release verification in the responses, the issue raised is the only issue that is keeping this from being a release. Given that, what is the actual difference between someone building this release candidate tag for themselves and an actual released version of the source? If it's a matter of not having binary tarballs for users, that could be fixed easily. Are we going to give less support to users because they are running an RC tag of an unreleased version?
> -----Original Message-----
> From: Josh Elser [mailto:josh.elser@gmail.com]
> Sent: Thursday, September 10, 2015 5:00 PM
> To: dev@accumulo.apache.org
> Subject: Re: [VOTE] Accumulo 1.5.4-rc1
>
> Well.. yeah. It is open source. I don't think you needed someone to tell you
> that though.
>
> There are lots of issues in telling people "just build the code yourself",
> probably the biggest being a rather negative experience for the user. For
> example, I'd be frustrated if I wanted to use MySQL and had to build it by
> hand to get a _data loss bugfix_.
>
> Going out on a limb and guessing that you're ultimately trying to say "it'll get
> released anyways", that doesn't address the fact that no one is actually
> volunteering to do the work.
>
> dlmarion@comcast.net wrote:
> > If the critical issues are fixed in 1.5.x, and someone needs them, can't they
> check out the source and build it themselves? Is that a viable option?
> >
> > ----- Original Message -----
> >
> > From: "Christopher"<ct...@apache.org>
> > To: dev@accumulo.apache.org
> > Sent: Thursday, September 10, 2015 3:44:20 PM
> > Subject: Re: [VOTE] Accumulo 1.5.4-rc1
> >
> > The larger concern I have is that expecting it to be fixed prior to
> > 1.5.4 might mean loss of willingness to create an RC2 for 1.5.4 and
> > release it at all. Recall, the 1.5 branch was only revived at all to
> > fix some critical issues and move on. It's still a viable alternative
> > to abandon 1.5.x and focus on fixing these issues in 1.6, and later,
> > where we've made dramatic improvements to the build. Fixing these
> > newly identified issues is going to take some time and effort. It's
> > not that it can't be done for 1.5.4... but the question is... who is going to do
> it? Is anybody who issued a "-1"
> > willing to step up and resolve these issues? Or will it rely on Josh?
> > I'm currently looking at some of the issues to try to help out if I
> > can, but I also have other obligations.
> >
> > On Thu, Sep 10, 2015 at 3:33 PM Alex Moundalexis<al...@cloudera.com>
> wrote:
> >
> >> -1 (non-binding)
> >>
> >> Fix now and it'll be fixed here and in 1.6.x.
> >>
> >> On Thu, Sep 10, 2015 at 2:46 AM, Sean Busbey<bu...@cloudera.com>
> wrote:
> >>
> >>> -1
> >>>
> >>> * signatures check out
> >>> * checksums match
> >>> * licensing errors noted in ACCUMULO-3988
> >>>
> >>> On Sat, Sep 5, 2015 at 4:27 PM, Josh Elser<el...@apache.org> wrote:
> >>>
> >>>> Accumulo Developers,
> >>>>
> >>>> Please consider the following candidate for Accumulo 1.5.4.
> >>>>
> >>>> Git Commit:
> >>>> 12a1041dcbb7f3b10543c305f27ece4b0d65ab9c
> >>>> Branch:
> >>>> 1.5.4-rc1
> >>>>
> >>>> If this vote passes, a gpg-signed tag will be created using:
> >>>> git tag -f -m 'Apache Accumulo 1.5.4' -s 1.5.4
> >>>> 12a1041dcbb7f3b10543c305f27ece4b0d65ab9c
> >>>>
> >>>> Staging repo:
> >>>>
> >> https://repository.apache.org/content/repositories/orgapacheaccumulo-
> >> 1039
> >>>> Source (official release artifact):
> >>>>
> >> https://repository.apache.org/content/repositories/orgapacheaccumulo-
> >> 1039/org/apache/accumulo/accumulo/1.5.4/accumulo-1.5.4-src.tar.gz
> >>>> Binary:
> >>>>
> >> https://repository.apache.org/content/repositories/orgapacheaccumulo-
> >> 1039/org/apache/accumulo/accumulo/1.5.4/accumulo-1.5.4-bin.tar.gz
> >>>> (Append ".sha1", ".md5", or ".asc" to download the signature/hash
> >>>> for a given artifact.)
> >>>>
> >>>> All artifacts were built and staged with:
> >>>> mvn release:prepare&& mvn release:perform
> >>>>
> >>>> Signing keys are available at
> >> https://www.apache.org/dist/accumulo/KEYS
> >>>> (Expected fingerprint:
> ABC8914C675FAD3FA74F39B2D146D62CAB471AE9)
> >>>>
> >>>> Release notes (in progress) can be found at
> >>>> https://accumulo.apache.org/release_notes/1.5.4
> >>>>
> >>>> Please vote one of:
> >>>> [ ] +1 - I have verified and accept...
> >>>> [ ] +0 - I have reservations, but not strong enough to vote against...
> >>>> [ ] -1 - Because..., I do not accept...
> >>>> ... these artifacts as the 1.5.4 release of Apache Accumulo.
> >>>>
> >>>> This vote will end on Thurs Sep 10 23:00:00 UTC 2015 (Thurs Sep 10
> >>>> 20:00:00 EDT 2015 / Thurs Sep 10 17:00:00 PDT 2015)
> >>>>
> >>>> Thanks!
> >>>>
> >>>> P.S. Hint: download the whole staging repo with wget -erobots=off
> >>>> -r -l inf -np -nH \
> >>>>
> >>>>
> >> https://repository.apache.org/content/repositories/orgapacheaccumulo-
> >> 1039/
> >>>> # note the trailing slash is needed
> >>>>
> >>>
> >>>
> >>> --
> >>> Sean
> >>>
> >
> >
Re: [VOTE] Accumulo 1.5.4-rc1
Posted by Josh Elser <jo...@gmail.com>.
Well.. yeah. It is open source. I don't think you needed someone to tell
you that though.
There are lots of issues in telling people "just build the code
yourself", probably the biggest being a rather negative experience for
the user. For example, I'd be frustrated if I wanted to use MySQL and
had to build it by hand to get a _data loss bugfix_.
Going out on a limb and guessing that you're ultimately trying to say
"it'll get released anyways", that doesn't address the fact that no one
is actually volunteering to do the work.
dlmarion@comcast.net wrote:
> If the critical issues are fixed in 1.5.x, and someone needs them, can't they check out the source and build it themselves? Is that a viable option?
>
> ----- Original Message -----
>
> From: "Christopher"<ct...@apache.org>
> To: dev@accumulo.apache.org
> Sent: Thursday, September 10, 2015 3:44:20 PM
> Subject: Re: [VOTE] Accumulo 1.5.4-rc1
>
> The larger concern I have is that expecting it to be fixed prior to 1.5.4
> might mean loss of willingness to create an RC2 for 1.5.4 and release it at
> all. Recall, the 1.5 branch was only revived at all to fix some critical
> issues and move on. It's still a viable alternative to abandon 1.5.x and
> focus on fixing these issues in 1.6, and later, where we've made dramatic
> improvements to the build. Fixing these newly identified issues is going to
> take some time and effort. It's not that it can't be done for 1.5.4... but
> the question is... who is going to do it? Is anybody who issued a "-1"
> willing to step up and resolve these issues? Or will it rely on Josh? I'm
> currently looking at some of the issues to try to help out if I can, but I
> also have other obligations.
>
> On Thu, Sep 10, 2015 at 3:33 PM Alex Moundalexis<al...@cloudera.com> wrote:
>
>> -1 (non-binding)
>>
>> Fix now and it'll be fixed here and in 1.6.x.
>>
>> On Thu, Sep 10, 2015 at 2:46 AM, Sean Busbey<bu...@cloudera.com> wrote:
>>
>>> -1
>>>
>>> * signatures check out
>>> * checksums match
>>> * licensing errors noted in ACCUMULO-3988
>>>
>>> On Sat, Sep 5, 2015 at 4:27 PM, Josh Elser<el...@apache.org> wrote:
>>>
>>>> Accumulo Developers,
>>>>
>>>> Please consider the following candidate for Accumulo 1.5.4.
>>>>
>>>> Git Commit:
>>>> 12a1041dcbb7f3b10543c305f27ece4b0d65ab9c
>>>> Branch:
>>>> 1.5.4-rc1
>>>>
>>>> If this vote passes, a gpg-signed tag will be created using:
>>>> git tag -f -m 'Apache Accumulo 1.5.4' -s 1.5.4
>>>> 12a1041dcbb7f3b10543c305f27ece4b0d65ab9c
>>>>
>>>> Staging repo:
>>>>
>> https://repository.apache.org/content/repositories/orgapacheaccumulo-1039
>>>> Source (official release artifact):
>>>>
>> https://repository.apache.org/content/repositories/orgapacheaccumulo-1039/org/apache/accumulo/accumulo/1.5.4/accumulo-1.5.4-src.tar.gz
>>>> Binary:
>>>>
>> https://repository.apache.org/content/repositories/orgapacheaccumulo-1039/org/apache/accumulo/accumulo/1.5.4/accumulo-1.5.4-bin.tar.gz
>>>> (Append ".sha1", ".md5", or ".asc" to download the signature/hash for a
>>>> given artifact.)
>>>>
>>>> All artifacts were built and staged with:
>>>> mvn release:prepare&& mvn release:perform
>>>>
>>>> Signing keys are available at
>> https://www.apache.org/dist/accumulo/KEYS
>>>> (Expected fingerprint: ABC8914C675FAD3FA74F39B2D146D62CAB471AE9)
>>>>
>>>> Release notes (in progress) can be found at
>>>> https://accumulo.apache.org/release_notes/1.5.4
>>>>
>>>> Please vote one of:
>>>> [ ] +1 - I have verified and accept...
>>>> [ ] +0 - I have reservations, but not strong enough to vote against...
>>>> [ ] -1 - Because..., I do not accept...
>>>> ... these artifacts as the 1.5.4 release of Apache Accumulo.
>>>>
>>>> This vote will end on Thurs Sep 10 23:00:00 UTC 2015
>>>> (Thurs Sep 10 20:00:00 EDT 2015 / Thurs Sep 10 17:00:00 PDT 2015)
>>>>
>>>> Thanks!
>>>>
>>>> P.S. Hint: download the whole staging repo with
>>>> wget -erobots=off -r -l inf -np -nH \
>>>>
>>>>
>> https://repository.apache.org/content/repositories/orgapacheaccumulo-1039/
>>>> # note the trailing slash is needed
>>>>
>>>
>>>
>>> --
>>> Sean
>>>
>
>
Re: [VOTE] Accumulo 1.5.4-rc1
Posted by dl...@comcast.net.
If the critical issues are fixed in 1.5.x, and someone needs them, can't they check out the source and build it themselves? Is that a viable option?
----- Original Message -----
From: "Christopher" <ct...@apache.org>
To: dev@accumulo.apache.org
Sent: Thursday, September 10, 2015 3:44:20 PM
Subject: Re: [VOTE] Accumulo 1.5.4-rc1
The larger concern I have is that expecting it to be fixed prior to 1.5.4
might mean loss of willingness to create an RC2 for 1.5.4 and release it at
all. Recall, the 1.5 branch was only revived at all to fix some critical
issues and move on. It's still a viable alternative to abandon 1.5.x and
focus on fixing these issues in 1.6, and later, where we've made dramatic
improvements to the build. Fixing these newly identified issues is going to
take some time and effort. It's not that it can't be done for 1.5.4... but
the question is... who is going to do it? Is anybody who issued a "-1"
willing to step up and resolve these issues? Or will it rely on Josh? I'm
currently looking at some of the issues to try to help out if I can, but I
also have other obligations.
On Thu, Sep 10, 2015 at 3:33 PM Alex Moundalexis <al...@cloudera.com> wrote:
> -1 (non-binding)
>
> Fix now and it'll be fixed here and in 1.6.x.
>
> On Thu, Sep 10, 2015 at 2:46 AM, Sean Busbey <bu...@cloudera.com> wrote:
>
> > -1
> >
> > * signatures check out
> > * checksums match
> > * licensing errors noted in ACCUMULO-3988
> >
> > On Sat, Sep 5, 2015 at 4:27 PM, Josh Elser <el...@apache.org> wrote:
> >
> > > Accumulo Developers,
> > >
> > > Please consider the following candidate for Accumulo 1.5.4.
> > >
> > > Git Commit:
> > > 12a1041dcbb7f3b10543c305f27ece4b0d65ab9c
> > > Branch:
> > > 1.5.4-rc1
> > >
> > > If this vote passes, a gpg-signed tag will be created using:
> > > git tag -f -m 'Apache Accumulo 1.5.4' -s 1.5.4
> > > 12a1041dcbb7f3b10543c305f27ece4b0d65ab9c
> > >
> > > Staging repo:
> > >
> >
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1039
> > > Source (official release artifact):
> > >
> >
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1039/org/apache/accumulo/accumulo/1.5.4/accumulo-1.5.4-src.tar.gz
> > > Binary:
> > >
> >
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1039/org/apache/accumulo/accumulo/1.5.4/accumulo-1.5.4-bin.tar.gz
> > > (Append ".sha1", ".md5", or ".asc" to download the signature/hash for a
> > > given artifact.)
> > >
> > > All artifacts were built and staged with:
> > > mvn release:prepare && mvn release:perform
> > >
> > > Signing keys are available at
> https://www.apache.org/dist/accumulo/KEYS
> > > (Expected fingerprint: ABC8914C675FAD3FA74F39B2D146D62CAB471AE9)
> > >
> > > Release notes (in progress) can be found at
> > > https://accumulo.apache.org/release_notes/1.5.4
> > >
> > > Please vote one of:
> > > [ ] +1 - I have verified and accept...
> > > [ ] +0 - I have reservations, but not strong enough to vote against...
> > > [ ] -1 - Because..., I do not accept...
> > > ... these artifacts as the 1.5.4 release of Apache Accumulo.
> > >
> > > This vote will end on Thurs Sep 10 23:00:00 UTC 2015
> > > (Thurs Sep 10 20:00:00 EDT 2015 / Thurs Sep 10 17:00:00 PDT 2015)
> > >
> > > Thanks!
> > >
> > > P.S. Hint: download the whole staging repo with
> > > wget -erobots=off -r -l inf -np -nH \
> > >
> > >
> >
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1039/
> > > # note the trailing slash is needed
> > >
> >
> >
> >
> > --
> > Sean
> >
>
Re: [VOTE] Accumulo 1.5.4-rc1
Posted by Christopher <ct...@apache.org>.
The larger concern I have is that expecting it to be fixed prior to 1.5.4
might mean loss of willingness to create an RC2 for 1.5.4 and release it at
all. Recall, the 1.5 branch was only revived at all to fix some critical
issues and move on. It's still a viable alternative to abandon 1.5.x and
focus on fixing these issues in 1.6, and later, where we've made dramatic
improvements to the build. Fixing these newly identified issues is going to
take some time and effort. It's not that it can't be done for 1.5.4... but
the question is... who is going to do it? Is anybody who issued a "-1"
willing to step up and resolve these issues? Or will it rely on Josh? I'm
currently looking at some of the issues to try to help out if I can, but I
also have other obligations.
On Thu, Sep 10, 2015 at 3:33 PM Alex Moundalexis <al...@cloudera.com> wrote:
> -1 (non-binding)
>
> Fix now and it'll be fixed here and in 1.6.x.
>
> On Thu, Sep 10, 2015 at 2:46 AM, Sean Busbey <bu...@cloudera.com> wrote:
>
> > -1
> >
> > * signatures check out
> > * checksums match
> > * licensing errors noted in ACCUMULO-3988
> >
> > On Sat, Sep 5, 2015 at 4:27 PM, Josh Elser <el...@apache.org> wrote:
> >
> > > Accumulo Developers,
> > >
> > > Please consider the following candidate for Accumulo 1.5.4.
> > >
> > > Git Commit:
> > > 12a1041dcbb7f3b10543c305f27ece4b0d65ab9c
> > > Branch:
> > > 1.5.4-rc1
> > >
> > > If this vote passes, a gpg-signed tag will be created using:
> > > git tag -f -m 'Apache Accumulo 1.5.4' -s 1.5.4
> > > 12a1041dcbb7f3b10543c305f27ece4b0d65ab9c
> > >
> > > Staging repo:
> > >
> >
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1039
> > > Source (official release artifact):
> > >
> >
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1039/org/apache/accumulo/accumulo/1.5.4/accumulo-1.5.4-src.tar.gz
> > > Binary:
> > >
> >
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1039/org/apache/accumulo/accumulo/1.5.4/accumulo-1.5.4-bin.tar.gz
> > > (Append ".sha1", ".md5", or ".asc" to download the signature/hash for a
> > > given artifact.)
> > >
> > > All artifacts were built and staged with:
> > > mvn release:prepare && mvn release:perform
> > >
> > > Signing keys are available at
> https://www.apache.org/dist/accumulo/KEYS
> > > (Expected fingerprint: ABC8914C675FAD3FA74F39B2D146D62CAB471AE9)
> > >
> > > Release notes (in progress) can be found at
> > > https://accumulo.apache.org/release_notes/1.5.4
> > >
> > > Please vote one of:
> > > [ ] +1 - I have verified and accept...
> > > [ ] +0 - I have reservations, but not strong enough to vote against...
> > > [ ] -1 - Because..., I do not accept...
> > > ... these artifacts as the 1.5.4 release of Apache Accumulo.
> > >
> > > This vote will end on Thurs Sep 10 23:00:00 UTC 2015
> > > (Thurs Sep 10 20:00:00 EDT 2015 / Thurs Sep 10 17:00:00 PDT 2015)
> > >
> > > Thanks!
> > >
> > > P.S. Hint: download the whole staging repo with
> > > wget -erobots=off -r -l inf -np -nH \
> > >
> > >
> >
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1039/
> > > # note the trailing slash is needed
> > >
> >
> >
> >
> > --
> > Sean
> >
>
Re: [VOTE] Accumulo 1.5.4-rc1
Posted by Alex Moundalexis <al...@cloudera.com>.
-1 (non-binding)
Fix now and it'll be fixed here and in 1.6.x.
On Thu, Sep 10, 2015 at 2:46 AM, Sean Busbey <bu...@cloudera.com> wrote:
> -1
>
> * signatures check out
> * checksums match
> * licensing errors noted in ACCUMULO-3988
>
> On Sat, Sep 5, 2015 at 4:27 PM, Josh Elser <el...@apache.org> wrote:
>
> > Accumulo Developers,
> >
> > Please consider the following candidate for Accumulo 1.5.4.
> >
> > Git Commit:
> > 12a1041dcbb7f3b10543c305f27ece4b0d65ab9c
> > Branch:
> > 1.5.4-rc1
> >
> > If this vote passes, a gpg-signed tag will be created using:
> > git tag -f -m 'Apache Accumulo 1.5.4' -s 1.5.4
> > 12a1041dcbb7f3b10543c305f27ece4b0d65ab9c
> >
> > Staging repo:
> >
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1039
> > Source (official release artifact):
> >
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1039/org/apache/accumulo/accumulo/1.5.4/accumulo-1.5.4-src.tar.gz
> > Binary:
> >
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1039/org/apache/accumulo/accumulo/1.5.4/accumulo-1.5.4-bin.tar.gz
> > (Append ".sha1", ".md5", or ".asc" to download the signature/hash for a
> > given artifact.)
> >
> > All artifacts were built and staged with:
> > mvn release:prepare && mvn release:perform
> >
> > Signing keys are available at https://www.apache.org/dist/accumulo/KEYS
> > (Expected fingerprint: ABC8914C675FAD3FA74F39B2D146D62CAB471AE9)
> >
> > Release notes (in progress) can be found at
> > https://accumulo.apache.org/release_notes/1.5.4
> >
> > Please vote one of:
> > [ ] +1 - I have verified and accept...
> > [ ] +0 - I have reservations, but not strong enough to vote against...
> > [ ] -1 - Because..., I do not accept...
> > ... these artifacts as the 1.5.4 release of Apache Accumulo.
> >
> > This vote will end on Thurs Sep 10 23:00:00 UTC 2015
> > (Thurs Sep 10 20:00:00 EDT 2015 / Thurs Sep 10 17:00:00 PDT 2015)
> >
> > Thanks!
> >
> > P.S. Hint: download the whole staging repo with
> > wget -erobots=off -r -l inf -np -nH \
> >
> >
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1039/
> > # note the trailing slash is needed
> >
>
>
>
> --
> Sean
>
Re: [VOTE] Accumulo 1.5.4-rc1
Posted by Sean Busbey <bu...@cloudera.com>.
We're responsible for all artifacts we distribute, both source releases and
generated binary artifacts.
It's also required that any binary bits we distribute are generated from
the approved source release. So licensing problems with them are problems
with the source release.
We could abstain from distributing the binary artifacts, but this vote
includes doing so. It'd be good form to also warn downstream users that the
generated binary artifacts aren't suitable for distribution.
--
Sean
On Sep 10, 2015 2:00 PM, "Josh Elser" <el...@apache.org> wrote:
> Uh, my understanding is that a binary jar by definition is not a
> foundation sponsored release (it's binary). Where's the docs/history on
> declaring a binary jar as an official release?
>
> The omission of sizzle.js's in LICENSE and copying Thrift's NOTICE into
> our NOTICE for the _official source_ release is still a problem.
>
> Sean Busbey wrote:
>
>> As members of the PMC, we're required to verify all releases we approve of
>> meet ASF licensing policy[1], so I don't consider the issues "minor".
>>
>> Mistakenly violating policy in the past is a different kind of problem
>> than
>> moving forward to knowingly violate it.
>>
>> In particular, not all of the bundled works have copyrights that are
>> covered under a donation to the Foundation. If we distribute e.g. the
>> accumulo-core binary jar in its current state the foundation will be
>> committing willful copyright infringement. The binary tarball (and I'd
>> imagine the rpm/deb files) have similar problems because we'd be violating
>> the terms of the included works' respective licenses.
>>
>>
>> [1]:
>> http://www.apache.org/dev/release.html#what-must-every-release-contain
>>
>> On Thu, Sep 10, 2015 at 11:51 AM, Billie Rinaldi<billie.rinaldi@gmail.com
>> >
>> wrote:
>>
>> Agreed.
>>>
>>> On Thu, Sep 10, 2015 at 9:47 AM, Christopher<ct...@apache.org>
>>> wrote:
>>>
>>> I think the license issues are relatively small compared to the bugfixes,
>>>> especially since we're really trying to close out 1.5.x development. So,
>>>> given the options, I'd prefer to pass RC1, and make the license fixes in
>>>> 1.6.x and later, as applicable.
>>>>
>>>> On Thu, Sep 10, 2015 at 12:28 PM Josh Elser<el...@apache.org> wrote:
>>>>
>>>> Thanks again for taking the time to inspect things so thoroughly, Sean.
>>>>>
>>>>> Others who have already voted, I'd ask for your opinion on whether we
>>>>> should sink this release (instead of me blindly going by majority
>>>>>
>>>> rule).
>>>
>>>> Personally, I'm presently of the opinion that, given the severity of
>>>>>
>>>> the
>>>
>>>> bug(s) fixed in this release already, RC1 should pass. Considering that
>>>>> we've been making releases like this for quite some time w/o issue and
>>>>> 1.5 is all but dead, let's push this release out, (again) table 1.5 and
>>>>> then make these improvements to 1.6 before we cut an RC there there
>>>>>
>>>> when
>>>
>>>> we have time to thoroughly vet the changes (instead of the 11th hour of
>>>>> a vote).
>>>>>
>>>>> If there's a need for lengthy discussion, let's break this off the VOTE
>>>>> thread (I leave this message here for visibility).
>>>>>
>>>>> - Josh
>>>>>
>>>>> Sean Busbey wrote:
>>>>>
>>>>>> -1
>>>>>>
>>>>>> * signatures check out
>>>>>> * checksums match
>>>>>> * licensing errors noted in ACCUMULO-3988
>>>>>>
>>>>>> On Sat, Sep 5, 2015 at 4:27 PM, Josh Elser<el...@apache.org>
>>>>>>
>>>>> wrote:
>>>
>>>> Accumulo Developers,
>>>>>>>
>>>>>>> Please consider the following candidate for Accumulo 1.5.4.
>>>>>>>
>>>>>>> Git Commit:
>>>>>>> 12a1041dcbb7f3b10543c305f27ece4b0d65ab9c
>>>>>>> Branch:
>>>>>>> 1.5.4-rc1
>>>>>>>
>>>>>>> If this vote passes, a gpg-signed tag will be created using:
>>>>>>> git tag -f -m 'Apache Accumulo 1.5.4' -s 1.5.4
>>>>>>> 12a1041dcbb7f3b10543c305f27ece4b0d65ab9c
>>>>>>>
>>>>>>> Staging repo:
>>>>>>>
>>>>>>>
>>> https://repository.apache.org/content/repositories/orgapacheaccumulo-1039
>>>
>>>> Source (official release artifact):
>>>>>>>
>>>>>>>
>>> https://repository.apache.org/content/repositories/orgapacheaccumulo-1039/org/apache/accumulo/accumulo/1.5.4/accumulo-1.5.4-src.tar.gz
>>>
>>>> Binary:
>>>>>>>
>>>>>>>
>>> https://repository.apache.org/content/repositories/orgapacheaccumulo-1039/org/apache/accumulo/accumulo/1.5.4/accumulo-1.5.4-bin.tar.gz
>>>
>>>> (Append ".sha1", ".md5", or ".asc" to download the signature/hash
>>>>>>>
>>>>>> for
>>>
>>>> a
>>>>
>>>>> given artifact.)
>>>>>>>
>>>>>>> All artifacts were built and staged with:
>>>>>>> mvn release:prepare&& mvn release:perform
>>>>>>>
>>>>>>> Signing keys are available at
>>>>>>>
>>>>>> https://www.apache.org/dist/accumulo/KEYS
>>>>
>>>>> (Expected fingerprint: ABC8914C675FAD3FA74F39B2D146D62CAB471AE9)
>>>>>>>
>>>>>>> Release notes (in progress) can be found at
>>>>>>> https://accumulo.apache.org/release_notes/1.5.4
>>>>>>>
>>>>>>> Please vote one of:
>>>>>>> [ ] +1 - I have verified and accept...
>>>>>>> [ ] +0 - I have reservations, but not strong enough to vote
>>>>>>>
>>>>>> against...
>>>
>>>> [ ] -1 - Because..., I do not accept...
>>>>>>> ... these artifacts as the 1.5.4 release of Apache Accumulo.
>>>>>>>
>>>>>>> This vote will end on Thurs Sep 10 23:00:00 UTC 2015
>>>>>>> (Thurs Sep 10 20:00:00 EDT 2015 / Thurs Sep 10 17:00:00 PDT 2015)
>>>>>>>
>>>>>>> Thanks!
>>>>>>>
>>>>>>> P.S. Hint: download the whole staging repo with
>>>>>>> wget -erobots=off -r -l inf -np -nH \
>>>>>>>
>>>>>>>
>>>>>>>
>>> https://repository.apache.org/content/repositories/orgapacheaccumulo-1039/
>>>
>>>> # note the trailing slash is needed
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>
>>
>>
Re: [VOTE] Accumulo 1.5.4-rc1
Posted by Mike Drob <md...@mdrob.com>.
-1.
Having correct licences is more important than even having code that
compiles (at release time).
On Thu, Sep 10, 2015 at 2:14 PM, Sean Busbey <bu...@cloudera.com> wrote:
> On Sep 10, 2015 2:07 PM, "Christopher" <ct...@apache.org> wrote:
> >
>
> >
> > However, I don't know where the "willful copyright infringement" comes
> > from. Omission of the LICENSE/NOTICE files is not necessarily an
> infringing
> > activity. They are acknowledgments/disclaimers of the legal status of the
> > code we use. As such, they do not generally change the rights we have to
> > redistribute under their respective licenses. They simply communicate
> them.
> > So, I think that part was a bit of hyperbole.
> >
>
> The bloomfilter code is included under a license that includes requirements
> about notifying where it came from. In the binary jar for accumulo-core we
> include no such notice about the provenance or copyright. That invalidates
> the license, which means we'd be distributing the work without a license in
> violation of the original authors' copyrights.
>
Re: [VOTE] Accumulo 1.5.4-rc1
Posted by Sean Busbey <bu...@cloudera.com>.
On Sep 10, 2015 2:07 PM, "Christopher" <ct...@apache.org> wrote:
>
>
> However, I don't know where the "willful copyright infringement" comes
> from. Omission of the LICENSE/NOTICE files is not necessarily an
infringing
> activity. They are acknowledgments/disclaimers of the legal status of the
> code we use. As such, they do not generally change the rights we have to
> redistribute under their respective licenses. They simply communicate
them.
> So, I think that part was a bit of hyperbole.
>
The bloomfilter code is included under a license that includes requirements
about notifying where it came from. In the binary jar for accumulo-core we
include no such notice about the provenance or copyright. That invalidates
the license, which means we'd be distributing the work without a license in
violation of the original authors' copyrights.
Re: [VOTE] Accumulo 1.5.4-rc1
Posted by Christopher <ct...@apache.org>.
Josh, the link Sean provided does address the issue of including
LICENSE/NOTICE files in the jars, and other associated artifacts. It also
makes it a point to call out that this expectation does not supersede the
definition of an ASF release as being source. That was a refresher I needed
as well.
However, I don't know where the "willful copyright infringement" comes
from. Omission of the LICENSE/NOTICE files is not necessarily an infringing
activity. They are acknowledgments/disclaimers of the legal status of the
code we use. As such, they do not generally change the rights we have to
redistribute under their respective licenses. They simply communicate them.
So, I think that part was a bit of hyperbole.
But yes, according to the policy cited, we do have an obligation to include
LICENSE/NOTICE files in the binaries.
On Thu, Sep 10, 2015 at 3:00 PM Josh Elser <el...@apache.org> wrote:
> Uh, my understanding is that a binary jar by definition is not a
> foundation sponsored release (it's binary). Where's the docs/history on
> declaring a binary jar as an official release?
>
> The omission of sizzle.js's in LICENSE and copying Thrift's NOTICE into
> our NOTICE for the _official source_ release is still a problem.
>
> Sean Busbey wrote:
> > As members of the PMC, we're required to verify all releases we approve
> of
> > meet ASF licensing policy[1], so I don't consider the issues "minor".
> >
> > Mistakenly violating policy in the past is a different kind of problem
> than
> > moving forward to knowingly violate it.
> >
> > In particular, not all of the bundled works have copyrights that are
> > covered under a donation to the Foundation. If we distribute e.g. the
> > accumulo-core binary jar in its current state the foundation will be
> > committing willful copyright infringement. The binary tarball (and I'd
> > imagine the rpm/deb files) have similar problems because we'd be
> violating
> > the terms of the included works' respective licenses.
> >
> >
> > [1]:
> http://www.apache.org/dev/release.html#what-must-every-release-contain
> >
> > On Thu, Sep 10, 2015 at 11:51 AM, Billie Rinaldi<
> billie.rinaldi@gmail.com>
> > wrote:
> >
> >> Agreed.
> >>
> >> On Thu, Sep 10, 2015 at 9:47 AM, Christopher<ct...@apache.org>
> wrote:
> >>
> >>> I think the license issues are relatively small compared to the
> bugfixes,
> >>> especially since we're really trying to close out 1.5.x development.
> So,
> >>> given the options, I'd prefer to pass RC1, and make the license fixes
> in
> >>> 1.6.x and later, as applicable.
> >>>
> >>> On Thu, Sep 10, 2015 at 12:28 PM Josh Elser<el...@apache.org> wrote:
> >>>
> >>>> Thanks again for taking the time to inspect things so thoroughly,
> Sean.
> >>>>
> >>>> Others who have already voted, I'd ask for your opinion on whether we
> >>>> should sink this release (instead of me blindly going by majority
> >> rule).
> >>>> Personally, I'm presently of the opinion that, given the severity of
> >> the
> >>>> bug(s) fixed in this release already, RC1 should pass. Considering
> that
> >>>> we've been making releases like this for quite some time w/o issue and
> >>>> 1.5 is all but dead, let's push this release out, (again) table 1.5
> and
> >>>> then make these improvements to 1.6 before we cut an RC there there
> >> when
> >>>> we have time to thoroughly vet the changes (instead of the 11th hour
> of
> >>>> a vote).
> >>>>
> >>>> If there's a need for lengthy discussion, let's break this off the
> VOTE
> >>>> thread (I leave this message here for visibility).
> >>>>
> >>>> - Josh
> >>>>
> >>>> Sean Busbey wrote:
> >>>>> -1
> >>>>>
> >>>>> * signatures check out
> >>>>> * checksums match
> >>>>> * licensing errors noted in ACCUMULO-3988
> >>>>>
> >>>>> On Sat, Sep 5, 2015 at 4:27 PM, Josh Elser<el...@apache.org>
> >> wrote:
> >>>>>> Accumulo Developers,
> >>>>>>
> >>>>>> Please consider the following candidate for Accumulo 1.5.4.
> >>>>>>
> >>>>>> Git Commit:
> >>>>>> 12a1041dcbb7f3b10543c305f27ece4b0d65ab9c
> >>>>>> Branch:
> >>>>>> 1.5.4-rc1
> >>>>>>
> >>>>>> If this vote passes, a gpg-signed tag will be created using:
> >>>>>> git tag -f -m 'Apache Accumulo 1.5.4' -s 1.5.4
> >>>>>> 12a1041dcbb7f3b10543c305f27ece4b0d65ab9c
> >>>>>>
> >>>>>> Staging repo:
> >>>>>>
> >>
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1039
> >>>>>> Source (official release artifact):
> >>>>>>
> >>
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1039/org/apache/accumulo/accumulo/1.5.4/accumulo-1.5.4-src.tar.gz
> >>>>>> Binary:
> >>>>>>
> >>
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1039/org/apache/accumulo/accumulo/1.5.4/accumulo-1.5.4-bin.tar.gz
> >>>>>> (Append ".sha1", ".md5", or ".asc" to download the signature/hash
> >> for
> >>> a
> >>>>>> given artifact.)
> >>>>>>
> >>>>>> All artifacts were built and staged with:
> >>>>>> mvn release:prepare&& mvn release:perform
> >>>>>>
> >>>>>> Signing keys are available at
> >>> https://www.apache.org/dist/accumulo/KEYS
> >>>>>> (Expected fingerprint: ABC8914C675FAD3FA74F39B2D146D62CAB471AE9)
> >>>>>>
> >>>>>> Release notes (in progress) can be found at
> >>>>>> https://accumulo.apache.org/release_notes/1.5.4
> >>>>>>
> >>>>>> Please vote one of:
> >>>>>> [ ] +1 - I have verified and accept...
> >>>>>> [ ] +0 - I have reservations, but not strong enough to vote
> >> against...
> >>>>>> [ ] -1 - Because..., I do not accept...
> >>>>>> ... these artifacts as the 1.5.4 release of Apache Accumulo.
> >>>>>>
> >>>>>> This vote will end on Thurs Sep 10 23:00:00 UTC 2015
> >>>>>> (Thurs Sep 10 20:00:00 EDT 2015 / Thurs Sep 10 17:00:00 PDT 2015)
> >>>>>>
> >>>>>> Thanks!
> >>>>>>
> >>>>>> P.S. Hint: download the whole staging repo with
> >>>>>> wget -erobots=off -r -l inf -np -nH \
> >>>>>>
> >>>>>>
> >>
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1039/
> >>>>>> # note the trailing slash is needed
> >>>>>>
> >>>>>
> >>>>>
> >
> >
> >
>
Re: [VOTE] Accumulo 1.5.4-rc1
Posted by Josh Elser <el...@apache.org>.
Uh, my understanding is that a binary jar by definition is not a
foundation sponsored release (it's binary). Where's the docs/history on
declaring a binary jar as an official release?
The omission of sizzle.js's in LICENSE and copying Thrift's NOTICE into
our NOTICE for the _official source_ release is still a problem.
Sean Busbey wrote:
> As members of the PMC, we're required to verify all releases we approve of
> meet ASF licensing policy[1], so I don't consider the issues "minor".
>
> Mistakenly violating policy in the past is a different kind of problem than
> moving forward to knowingly violate it.
>
> In particular, not all of the bundled works have copyrights that are
> covered under a donation to the Foundation. If we distribute e.g. the
> accumulo-core binary jar in its current state the foundation will be
> committing willful copyright infringement. The binary tarball (and I'd
> imagine the rpm/deb files) have similar problems because we'd be violating
> the terms of the included works' respective licenses.
>
>
> [1]: http://www.apache.org/dev/release.html#what-must-every-release-contain
>
> On Thu, Sep 10, 2015 at 11:51 AM, Billie Rinaldi<bi...@gmail.com>
> wrote:
>
>> Agreed.
>>
>> On Thu, Sep 10, 2015 at 9:47 AM, Christopher<ct...@apache.org> wrote:
>>
>>> I think the license issues are relatively small compared to the bugfixes,
>>> especially since we're really trying to close out 1.5.x development. So,
>>> given the options, I'd prefer to pass RC1, and make the license fixes in
>>> 1.6.x and later, as applicable.
>>>
>>> On Thu, Sep 10, 2015 at 12:28 PM Josh Elser<el...@apache.org> wrote:
>>>
>>>> Thanks again for taking the time to inspect things so thoroughly, Sean.
>>>>
>>>> Others who have already voted, I'd ask for your opinion on whether we
>>>> should sink this release (instead of me blindly going by majority
>> rule).
>>>> Personally, I'm presently of the opinion that, given the severity of
>> the
>>>> bug(s) fixed in this release already, RC1 should pass. Considering that
>>>> we've been making releases like this for quite some time w/o issue and
>>>> 1.5 is all but dead, let's push this release out, (again) table 1.5 and
>>>> then make these improvements to 1.6 before we cut an RC there there
>> when
>>>> we have time to thoroughly vet the changes (instead of the 11th hour of
>>>> a vote).
>>>>
>>>> If there's a need for lengthy discussion, let's break this off the VOTE
>>>> thread (I leave this message here for visibility).
>>>>
>>>> - Josh
>>>>
>>>> Sean Busbey wrote:
>>>>> -1
>>>>>
>>>>> * signatures check out
>>>>> * checksums match
>>>>> * licensing errors noted in ACCUMULO-3988
>>>>>
>>>>> On Sat, Sep 5, 2015 at 4:27 PM, Josh Elser<el...@apache.org>
>> wrote:
>>>>>> Accumulo Developers,
>>>>>>
>>>>>> Please consider the following candidate for Accumulo 1.5.4.
>>>>>>
>>>>>> Git Commit:
>>>>>> 12a1041dcbb7f3b10543c305f27ece4b0d65ab9c
>>>>>> Branch:
>>>>>> 1.5.4-rc1
>>>>>>
>>>>>> If this vote passes, a gpg-signed tag will be created using:
>>>>>> git tag -f -m 'Apache Accumulo 1.5.4' -s 1.5.4
>>>>>> 12a1041dcbb7f3b10543c305f27ece4b0d65ab9c
>>>>>>
>>>>>> Staging repo:
>>>>>>
>> https://repository.apache.org/content/repositories/orgapacheaccumulo-1039
>>>>>> Source (official release artifact):
>>>>>>
>> https://repository.apache.org/content/repositories/orgapacheaccumulo-1039/org/apache/accumulo/accumulo/1.5.4/accumulo-1.5.4-src.tar.gz
>>>>>> Binary:
>>>>>>
>> https://repository.apache.org/content/repositories/orgapacheaccumulo-1039/org/apache/accumulo/accumulo/1.5.4/accumulo-1.5.4-bin.tar.gz
>>>>>> (Append ".sha1", ".md5", or ".asc" to download the signature/hash
>> for
>>> a
>>>>>> given artifact.)
>>>>>>
>>>>>> All artifacts were built and staged with:
>>>>>> mvn release:prepare&& mvn release:perform
>>>>>>
>>>>>> Signing keys are available at
>>> https://www.apache.org/dist/accumulo/KEYS
>>>>>> (Expected fingerprint: ABC8914C675FAD3FA74F39B2D146D62CAB471AE9)
>>>>>>
>>>>>> Release notes (in progress) can be found at
>>>>>> https://accumulo.apache.org/release_notes/1.5.4
>>>>>>
>>>>>> Please vote one of:
>>>>>> [ ] +1 - I have verified and accept...
>>>>>> [ ] +0 - I have reservations, but not strong enough to vote
>> against...
>>>>>> [ ] -1 - Because..., I do not accept...
>>>>>> ... these artifacts as the 1.5.4 release of Apache Accumulo.
>>>>>>
>>>>>> This vote will end on Thurs Sep 10 23:00:00 UTC 2015
>>>>>> (Thurs Sep 10 20:00:00 EDT 2015 / Thurs Sep 10 17:00:00 PDT 2015)
>>>>>>
>>>>>> Thanks!
>>>>>>
>>>>>> P.S. Hint: download the whole staging repo with
>>>>>> wget -erobots=off -r -l inf -np -nH \
>>>>>>
>>>>>>
>> https://repository.apache.org/content/repositories/orgapacheaccumulo-1039/
>>>>>> # note the trailing slash is needed
>>>>>>
>>>>>
>>>>>
>
>
>
Re: [VOTE] Accumulo 1.5.4-rc1
Posted by Christopher <ct...@apache.org>.
I'm not suggesting ignoring the issues. I was suggesting prioritizing them
after careful consideration, like we would any other problem.
On Thu, Sep 10, 2015 at 2:49 PM John Vines <vi...@apache.org> wrote:
> -1
>
> I'm with Sean on this one. Ignoring now known licensing issues because we
> hadn't handled them in the past is not a valid excuse.
>
> On Thu, Sep 10, 2015 at 2:27 PM Sean Busbey <bu...@cloudera.com> wrote:
>
> > As members of the PMC, we're required to verify all releases we approve
> of
> > meet ASF licensing policy[1], so I don't consider the issues "minor".
> >
> > Mistakenly violating policy in the past is a different kind of problem
> than
> > moving forward to knowingly violate it.
> >
> > In particular, not all of the bundled works have copyrights that are
> > covered under a donation to the Foundation. If we distribute e.g. the
> > accumulo-core binary jar in its current state the foundation will be
> > committing willful copyright infringement. The binary tarball (and I'd
> > imagine the rpm/deb files) have similar problems because we'd be
> violating
> > the terms of the included works' respective licenses.
> >
> >
> > [1]:
> > http://www.apache.org/dev/release.html#what-must-every-release-contain
> >
> > On Thu, Sep 10, 2015 at 11:51 AM, Billie Rinaldi <
> billie.rinaldi@gmail.com
> > >
> > wrote:
> >
> > > Agreed.
> > >
> > > On Thu, Sep 10, 2015 at 9:47 AM, Christopher <ct...@apache.org>
> > wrote:
> > >
> > > > I think the license issues are relatively small compared to the
> > bugfixes,
> > > > especially since we're really trying to close out 1.5.x development.
> > So,
> > > > given the options, I'd prefer to pass RC1, and make the license fixes
> > in
> > > > 1.6.x and later, as applicable.
> > > >
> > > > On Thu, Sep 10, 2015 at 12:28 PM Josh Elser <el...@apache.org>
> wrote:
> > > >
> > > > > Thanks again for taking the time to inspect things so thoroughly,
> > Sean.
> > > > >
> > > > > Others who have already voted, I'd ask for your opinion on whether
> we
> > > > > should sink this release (instead of me blindly going by majority
> > > rule).
> > > > >
> > > > > Personally, I'm presently of the opinion that, given the severity
> of
> > > the
> > > > > bug(s) fixed in this release already, RC1 should pass. Considering
> > that
> > > > > we've been making releases like this for quite some time w/o issue
> > and
> > > > > 1.5 is all but dead, let's push this release out, (again) table 1.5
> > and
> > > > > then make these improvements to 1.6 before we cut an RC there there
> > > when
> > > > > we have time to thoroughly vet the changes (instead of the 11th
> hour
> > of
> > > > > a vote).
> > > > >
> > > > > If there's a need for lengthy discussion, let's break this off the
> > VOTE
> > > > > thread (I leave this message here for visibility).
> > > > >
> > > > > - Josh
> > > > >
> > > > > Sean Busbey wrote:
> > > > > > -1
> > > > > >
> > > > > > * signatures check out
> > > > > > * checksums match
> > > > > > * licensing errors noted in ACCUMULO-3988
> > > > > >
> > > > > > On Sat, Sep 5, 2015 at 4:27 PM, Josh Elser<el...@apache.org>
> > > wrote:
> > > > > >
> > > > > >> Accumulo Developers,
> > > > > >>
> > > > > >> Please consider the following candidate for Accumulo 1.5.4.
> > > > > >>
> > > > > >> Git Commit:
> > > > > >> 12a1041dcbb7f3b10543c305f27ece4b0d65ab9c
> > > > > >> Branch:
> > > > > >> 1.5.4-rc1
> > > > > >>
> > > > > >> If this vote passes, a gpg-signed tag will be created using:
> > > > > >> git tag -f -m 'Apache Accumulo 1.5.4' -s 1.5.4
> > > > > >> 12a1041dcbb7f3b10543c305f27ece4b0d65ab9c
> > > > > >>
> > > > > >> Staging repo:
> > > > > >>
> > > > >
> > > >
> > >
> >
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1039
> > > > > >> Source (official release artifact):
> > > > > >>
> > > > >
> > > >
> > >
> >
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1039/org/apache/accumulo/accumulo/1.5.4/accumulo-1.5.4-src.tar.gz
> > > > > >> Binary:
> > > > > >>
> > > > >
> > > >
> > >
> >
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1039/org/apache/accumulo/accumulo/1.5.4/accumulo-1.5.4-bin.tar.gz
> > > > > >> (Append ".sha1", ".md5", or ".asc" to download the
> signature/hash
> > > for
> > > > a
> > > > > >> given artifact.)
> > > > > >>
> > > > > >> All artifacts were built and staged with:
> > > > > >> mvn release:prepare&& mvn release:perform
> > > > > >>
> > > > > >> Signing keys are available at
> > > > https://www.apache.org/dist/accumulo/KEYS
> > > > > >> (Expected fingerprint: ABC8914C675FAD3FA74F39B2D146D62CAB471AE9)
> > > > > >>
> > > > > >> Release notes (in progress) can be found at
> > > > > >> https://accumulo.apache.org/release_notes/1.5.4
> > > > > >>
> > > > > >> Please vote one of:
> > > > > >> [ ] +1 - I have verified and accept...
> > > > > >> [ ] +0 - I have reservations, but not strong enough to vote
> > > against...
> > > > > >> [ ] -1 - Because..., I do not accept...
> > > > > >> ... these artifacts as the 1.5.4 release of Apache Accumulo.
> > > > > >>
> > > > > >> This vote will end on Thurs Sep 10 23:00:00 UTC 2015
> > > > > >> (Thurs Sep 10 20:00:00 EDT 2015 / Thurs Sep 10 17:00:00 PDT
> > 2015)
> > > > > >>
> > > > > >> Thanks!
> > > > > >>
> > > > > >> P.S. Hint: download the whole staging repo with
> > > > > >> wget -erobots=off -r -l inf -np -nH \
> > > > > >>
> > > > > >>
> > > > >
> > > >
> > >
> >
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1039/
> > > > > >> # note the trailing slash is needed
> > > > > >>
> > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> >
> >
> > --
> > Sean
> >
>
Re: [VOTE] Accumulo 1.5.4-rc1
Posted by Josh Elser <el...@apache.org>.
Michael,
I'd take some time to catch up on some mailing lists like
general@incubator before passing judgement like that. It's rather hasty.
Michael Ridley wrote:
> -1 (nonbinding)
>
> I agree, license issues are important and it sounds like the ASF policy
> doesn't leave a lot of room for interpretation
>
> On Thu, Sep 10, 2015 at 2:49 PM, John Vines<vi...@apache.org> wrote:
>
>> -1
>>
>> I'm with Sean on this one. Ignoring now known licensing issues because we
>> hadn't handled them in the past is not a valid excuse.
>>
>> On Thu, Sep 10, 2015 at 2:27 PM Sean Busbey<bu...@cloudera.com> wrote:
>>
>>> As members of the PMC, we're required to verify all releases we approve
>> of
>>> meet ASF licensing policy[1], so I don't consider the issues "minor".
>>>
>>> Mistakenly violating policy in the past is a different kind of problem
>> than
>>> moving forward to knowingly violate it.
>>>
>>> In particular, not all of the bundled works have copyrights that are
>>> covered under a donation to the Foundation. If we distribute e.g. the
>>> accumulo-core binary jar in its current state the foundation will be
>>> committing willful copyright infringement. The binary tarball (and I'd
>>> imagine the rpm/deb files) have similar problems because we'd be
>> violating
>>> the terms of the included works' respective licenses.
>>>
>>>
>>> [1]:
>>> http://www.apache.org/dev/release.html#what-must-every-release-contain
>>>
>>> On Thu, Sep 10, 2015 at 11:51 AM, Billie Rinaldi<
>> billie.rinaldi@gmail.com
>>> wrote:
>>>
>>>> Agreed.
>>>>
>>>> On Thu, Sep 10, 2015 at 9:47 AM, Christopher<ct...@apache.org>
>>> wrote:
>>>>> I think the license issues are relatively small compared to the
>>> bugfixes,
>>>>> especially since we're really trying to close out 1.5.x development.
>>> So,
>>>>> given the options, I'd prefer to pass RC1, and make the license fixes
>>> in
>>>>> 1.6.x and later, as applicable.
>>>>>
>>>>> On Thu, Sep 10, 2015 at 12:28 PM Josh Elser<el...@apache.org>
>> wrote:
>>>>>> Thanks again for taking the time to inspect things so thoroughly,
>>> Sean.
>>>>>> Others who have already voted, I'd ask for your opinion on whether
>> we
>>>>>> should sink this release (instead of me blindly going by majority
>>>> rule).
>>>>>> Personally, I'm presently of the opinion that, given the severity
>> of
>>>> the
>>>>>> bug(s) fixed in this release already, RC1 should pass. Considering
>>> that
>>>>>> we've been making releases like this for quite some time w/o issue
>>> and
>>>>>> 1.5 is all but dead, let's push this release out, (again) table 1.5
>>> and
>>>>>> then make these improvements to 1.6 before we cut an RC there there
>>>> when
>>>>>> we have time to thoroughly vet the changes (instead of the 11th
>> hour
>>> of
>>>>>> a vote).
>>>>>>
>>>>>> If there's a need for lengthy discussion, let's break this off the
>>> VOTE
>>>>>> thread (I leave this message here for visibility).
>>>>>>
>>>>>> - Josh
>>>>>>
>>>>>> Sean Busbey wrote:
>>>>>>> -1
>>>>>>>
>>>>>>> * signatures check out
>>>>>>> * checksums match
>>>>>>> * licensing errors noted in ACCUMULO-3988
>>>>>>>
>>>>>>> On Sat, Sep 5, 2015 at 4:27 PM, Josh Elser<el...@apache.org>
>>>> wrote:
>>>>>>>> Accumulo Developers,
>>>>>>>>
>>>>>>>> Please consider the following candidate for Accumulo 1.5.4.
>>>>>>>>
>>>>>>>> Git Commit:
>>>>>>>> 12a1041dcbb7f3b10543c305f27ece4b0d65ab9c
>>>>>>>> Branch:
>>>>>>>> 1.5.4-rc1
>>>>>>>>
>>>>>>>> If this vote passes, a gpg-signed tag will be created using:
>>>>>>>> git tag -f -m 'Apache Accumulo 1.5.4' -s 1.5.4
>>>>>>>> 12a1041dcbb7f3b10543c305f27ece4b0d65ab9c
>>>>>>>>
>>>>>>>> Staging repo:
>>>>>>>>
>> https://repository.apache.org/content/repositories/orgapacheaccumulo-1039
>>>>>>>> Source (official release artifact):
>>>>>>>>
>> https://repository.apache.org/content/repositories/orgapacheaccumulo-1039/org/apache/accumulo/accumulo/1.5.4/accumulo-1.5.4-src.tar.gz
>>>>>>>> Binary:
>>>>>>>>
>> https://repository.apache.org/content/repositories/orgapacheaccumulo-1039/org/apache/accumulo/accumulo/1.5.4/accumulo-1.5.4-bin.tar.gz
>>>>>>>> (Append ".sha1", ".md5", or ".asc" to download the
>> signature/hash
>>>> for
>>>>> a
>>>>>>>> given artifact.)
>>>>>>>>
>>>>>>>> All artifacts were built and staged with:
>>>>>>>> mvn release:prepare&& mvn release:perform
>>>>>>>>
>>>>>>>> Signing keys are available at
>>>>> https://www.apache.org/dist/accumulo/KEYS
>>>>>>>> (Expected fingerprint: ABC8914C675FAD3FA74F39B2D146D62CAB471AE9)
>>>>>>>>
>>>>>>>> Release notes (in progress) can be found at
>>>>>>>> https://accumulo.apache.org/release_notes/1.5.4
>>>>>>>>
>>>>>>>> Please vote one of:
>>>>>>>> [ ] +1 - I have verified and accept...
>>>>>>>> [ ] +0 - I have reservations, but not strong enough to vote
>>>> against...
>>>>>>>> [ ] -1 - Because..., I do not accept...
>>>>>>>> ... these artifacts as the 1.5.4 release of Apache Accumulo.
>>>>>>>>
>>>>>>>> This vote will end on Thurs Sep 10 23:00:00 UTC 2015
>>>>>>>> (Thurs Sep 10 20:00:00 EDT 2015 / Thurs Sep 10 17:00:00 PDT
>>> 2015)
>>>>>>>> Thanks!
>>>>>>>>
>>>>>>>> P.S. Hint: download the whole staging repo with
>>>>>>>> wget -erobots=off -r -l inf -np -nH \
>>>>>>>>
>>>>>>>>
>> https://repository.apache.org/content/repositories/orgapacheaccumulo-1039/
>>>>>>>> # note the trailing slash is needed
>>>>>>>>
>>>>>>>
>>>>>>>
>>>
>>>
>>> --
>>> Sean
>>>
>
>
>
Re: [VOTE] Accumulo 1.5.4-rc1
Posted by Michael Ridley <mr...@clouderagovt.com>.
-1 (nonbinding)
I agree, license issues are important and it sounds like the ASF policy
doesn't leave a lot of room for interpretation
On Thu, Sep 10, 2015 at 2:49 PM, John Vines <vi...@apache.org> wrote:
> -1
>
> I'm with Sean on this one. Ignoring now known licensing issues because we
> hadn't handled them in the past is not a valid excuse.
>
> On Thu, Sep 10, 2015 at 2:27 PM Sean Busbey <bu...@cloudera.com> wrote:
>
> > As members of the PMC, we're required to verify all releases we approve
> of
> > meet ASF licensing policy[1], so I don't consider the issues "minor".
> >
> > Mistakenly violating policy in the past is a different kind of problem
> than
> > moving forward to knowingly violate it.
> >
> > In particular, not all of the bundled works have copyrights that are
> > covered under a donation to the Foundation. If we distribute e.g. the
> > accumulo-core binary jar in its current state the foundation will be
> > committing willful copyright infringement. The binary tarball (and I'd
> > imagine the rpm/deb files) have similar problems because we'd be
> violating
> > the terms of the included works' respective licenses.
> >
> >
> > [1]:
> > http://www.apache.org/dev/release.html#what-must-every-release-contain
> >
> > On Thu, Sep 10, 2015 at 11:51 AM, Billie Rinaldi <
> billie.rinaldi@gmail.com
> > >
> > wrote:
> >
> > > Agreed.
> > >
> > > On Thu, Sep 10, 2015 at 9:47 AM, Christopher <ct...@apache.org>
> > wrote:
> > >
> > > > I think the license issues are relatively small compared to the
> > bugfixes,
> > > > especially since we're really trying to close out 1.5.x development.
> > So,
> > > > given the options, I'd prefer to pass RC1, and make the license fixes
> > in
> > > > 1.6.x and later, as applicable.
> > > >
> > > > On Thu, Sep 10, 2015 at 12:28 PM Josh Elser <el...@apache.org>
> wrote:
> > > >
> > > > > Thanks again for taking the time to inspect things so thoroughly,
> > Sean.
> > > > >
> > > > > Others who have already voted, I'd ask for your opinion on whether
> we
> > > > > should sink this release (instead of me blindly going by majority
> > > rule).
> > > > >
> > > > > Personally, I'm presently of the opinion that, given the severity
> of
> > > the
> > > > > bug(s) fixed in this release already, RC1 should pass. Considering
> > that
> > > > > we've been making releases like this for quite some time w/o issue
> > and
> > > > > 1.5 is all but dead, let's push this release out, (again) table 1.5
> > and
> > > > > then make these improvements to 1.6 before we cut an RC there there
> > > when
> > > > > we have time to thoroughly vet the changes (instead of the 11th
> hour
> > of
> > > > > a vote).
> > > > >
> > > > > If there's a need for lengthy discussion, let's break this off the
> > VOTE
> > > > > thread (I leave this message here for visibility).
> > > > >
> > > > > - Josh
> > > > >
> > > > > Sean Busbey wrote:
> > > > > > -1
> > > > > >
> > > > > > * signatures check out
> > > > > > * checksums match
> > > > > > * licensing errors noted in ACCUMULO-3988
> > > > > >
> > > > > > On Sat, Sep 5, 2015 at 4:27 PM, Josh Elser<el...@apache.org>
> > > wrote:
> > > > > >
> > > > > >> Accumulo Developers,
> > > > > >>
> > > > > >> Please consider the following candidate for Accumulo 1.5.4.
> > > > > >>
> > > > > >> Git Commit:
> > > > > >> 12a1041dcbb7f3b10543c305f27ece4b0d65ab9c
> > > > > >> Branch:
> > > > > >> 1.5.4-rc1
> > > > > >>
> > > > > >> If this vote passes, a gpg-signed tag will be created using:
> > > > > >> git tag -f -m 'Apache Accumulo 1.5.4' -s 1.5.4
> > > > > >> 12a1041dcbb7f3b10543c305f27ece4b0d65ab9c
> > > > > >>
> > > > > >> Staging repo:
> > > > > >>
> > > > >
> > > >
> > >
> >
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1039
> > > > > >> Source (official release artifact):
> > > > > >>
> > > > >
> > > >
> > >
> >
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1039/org/apache/accumulo/accumulo/1.5.4/accumulo-1.5.4-src.tar.gz
> > > > > >> Binary:
> > > > > >>
> > > > >
> > > >
> > >
> >
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1039/org/apache/accumulo/accumulo/1.5.4/accumulo-1.5.4-bin.tar.gz
> > > > > >> (Append ".sha1", ".md5", or ".asc" to download the
> signature/hash
> > > for
> > > > a
> > > > > >> given artifact.)
> > > > > >>
> > > > > >> All artifacts were built and staged with:
> > > > > >> mvn release:prepare&& mvn release:perform
> > > > > >>
> > > > > >> Signing keys are available at
> > > > https://www.apache.org/dist/accumulo/KEYS
> > > > > >> (Expected fingerprint: ABC8914C675FAD3FA74F39B2D146D62CAB471AE9)
> > > > > >>
> > > > > >> Release notes (in progress) can be found at
> > > > > >> https://accumulo.apache.org/release_notes/1.5.4
> > > > > >>
> > > > > >> Please vote one of:
> > > > > >> [ ] +1 - I have verified and accept...
> > > > > >> [ ] +0 - I have reservations, but not strong enough to vote
> > > against...
> > > > > >> [ ] -1 - Because..., I do not accept...
> > > > > >> ... these artifacts as the 1.5.4 release of Apache Accumulo.
> > > > > >>
> > > > > >> This vote will end on Thurs Sep 10 23:00:00 UTC 2015
> > > > > >> (Thurs Sep 10 20:00:00 EDT 2015 / Thurs Sep 10 17:00:00 PDT
> > 2015)
> > > > > >>
> > > > > >> Thanks!
> > > > > >>
> > > > > >> P.S. Hint: download the whole staging repo with
> > > > > >> wget -erobots=off -r -l inf -np -nH \
> > > > > >>
> > > > > >>
> > > > >
> > > >
> > >
> >
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1039/
> > > > > >> # note the trailing slash is needed
> > > > > >>
> > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> >
> >
> > --
> > Sean
> >
>
--
Michael Ridley <mr...@clouderagovt.com> mobile: (571) 438-2420
Solutions Architect
Cloudera Government Solutions Inc.
Re: [VOTE] Accumulo 1.5.4-rc1
Posted by John Vines <vi...@apache.org>.
-1
I'm with Sean on this one. Ignoring now known licensing issues because we
hadn't handled them in the past is not a valid excuse.
On Thu, Sep 10, 2015 at 2:27 PM Sean Busbey <bu...@cloudera.com> wrote:
> As members of the PMC, we're required to verify all releases we approve of
> meet ASF licensing policy[1], so I don't consider the issues "minor".
>
> Mistakenly violating policy in the past is a different kind of problem than
> moving forward to knowingly violate it.
>
> In particular, not all of the bundled works have copyrights that are
> covered under a donation to the Foundation. If we distribute e.g. the
> accumulo-core binary jar in its current state the foundation will be
> committing willful copyright infringement. The binary tarball (and I'd
> imagine the rpm/deb files) have similar problems because we'd be violating
> the terms of the included works' respective licenses.
>
>
> [1]:
> http://www.apache.org/dev/release.html#what-must-every-release-contain
>
> On Thu, Sep 10, 2015 at 11:51 AM, Billie Rinaldi <billie.rinaldi@gmail.com
> >
> wrote:
>
> > Agreed.
> >
> > On Thu, Sep 10, 2015 at 9:47 AM, Christopher <ct...@apache.org>
> wrote:
> >
> > > I think the license issues are relatively small compared to the
> bugfixes,
> > > especially since we're really trying to close out 1.5.x development.
> So,
> > > given the options, I'd prefer to pass RC1, and make the license fixes
> in
> > > 1.6.x and later, as applicable.
> > >
> > > On Thu, Sep 10, 2015 at 12:28 PM Josh Elser <el...@apache.org> wrote:
> > >
> > > > Thanks again for taking the time to inspect things so thoroughly,
> Sean.
> > > >
> > > > Others who have already voted, I'd ask for your opinion on whether we
> > > > should sink this release (instead of me blindly going by majority
> > rule).
> > > >
> > > > Personally, I'm presently of the opinion that, given the severity of
> > the
> > > > bug(s) fixed in this release already, RC1 should pass. Considering
> that
> > > > we've been making releases like this for quite some time w/o issue
> and
> > > > 1.5 is all but dead, let's push this release out, (again) table 1.5
> and
> > > > then make these improvements to 1.6 before we cut an RC there there
> > when
> > > > we have time to thoroughly vet the changes (instead of the 11th hour
> of
> > > > a vote).
> > > >
> > > > If there's a need for lengthy discussion, let's break this off the
> VOTE
> > > > thread (I leave this message here for visibility).
> > > >
> > > > - Josh
> > > >
> > > > Sean Busbey wrote:
> > > > > -1
> > > > >
> > > > > * signatures check out
> > > > > * checksums match
> > > > > * licensing errors noted in ACCUMULO-3988
> > > > >
> > > > > On Sat, Sep 5, 2015 at 4:27 PM, Josh Elser<el...@apache.org>
> > wrote:
> > > > >
> > > > >> Accumulo Developers,
> > > > >>
> > > > >> Please consider the following candidate for Accumulo 1.5.4.
> > > > >>
> > > > >> Git Commit:
> > > > >> 12a1041dcbb7f3b10543c305f27ece4b0d65ab9c
> > > > >> Branch:
> > > > >> 1.5.4-rc1
> > > > >>
> > > > >> If this vote passes, a gpg-signed tag will be created using:
> > > > >> git tag -f -m 'Apache Accumulo 1.5.4' -s 1.5.4
> > > > >> 12a1041dcbb7f3b10543c305f27ece4b0d65ab9c
> > > > >>
> > > > >> Staging repo:
> > > > >>
> > > >
> > >
> >
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1039
> > > > >> Source (official release artifact):
> > > > >>
> > > >
> > >
> >
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1039/org/apache/accumulo/accumulo/1.5.4/accumulo-1.5.4-src.tar.gz
> > > > >> Binary:
> > > > >>
> > > >
> > >
> >
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1039/org/apache/accumulo/accumulo/1.5.4/accumulo-1.5.4-bin.tar.gz
> > > > >> (Append ".sha1", ".md5", or ".asc" to download the signature/hash
> > for
> > > a
> > > > >> given artifact.)
> > > > >>
> > > > >> All artifacts were built and staged with:
> > > > >> mvn release:prepare&& mvn release:perform
> > > > >>
> > > > >> Signing keys are available at
> > > https://www.apache.org/dist/accumulo/KEYS
> > > > >> (Expected fingerprint: ABC8914C675FAD3FA74F39B2D146D62CAB471AE9)
> > > > >>
> > > > >> Release notes (in progress) can be found at
> > > > >> https://accumulo.apache.org/release_notes/1.5.4
> > > > >>
> > > > >> Please vote one of:
> > > > >> [ ] +1 - I have verified and accept...
> > > > >> [ ] +0 - I have reservations, but not strong enough to vote
> > against...
> > > > >> [ ] -1 - Because..., I do not accept...
> > > > >> ... these artifacts as the 1.5.4 release of Apache Accumulo.
> > > > >>
> > > > >> This vote will end on Thurs Sep 10 23:00:00 UTC 2015
> > > > >> (Thurs Sep 10 20:00:00 EDT 2015 / Thurs Sep 10 17:00:00 PDT
> 2015)
> > > > >>
> > > > >> Thanks!
> > > > >>
> > > > >> P.S. Hint: download the whole staging repo with
> > > > >> wget -erobots=off -r -l inf -np -nH \
> > > > >>
> > > > >>
> > > >
> > >
> >
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1039/
> > > > >> # note the trailing slash is needed
> > > > >>
> > > > >
> > > > >
> > > > >
> > > >
> > >
> >
>
>
>
> --
> Sean
>
Re: [VOTE] Accumulo 1.5.4-rc1
Posted by Sean Busbey <bu...@cloudera.com>.
As members of the PMC, we're required to verify all releases we approve of
meet ASF licensing policy[1], so I don't consider the issues "minor".
Mistakenly violating policy in the past is a different kind of problem than
moving forward to knowingly violate it.
In particular, not all of the bundled works have copyrights that are
covered under a donation to the Foundation. If we distribute e.g. the
accumulo-core binary jar in its current state the foundation will be
committing willful copyright infringement. The binary tarball (and I'd
imagine the rpm/deb files) have similar problems because we'd be violating
the terms of the included works' respective licenses.
[1]: http://www.apache.org/dev/release.html#what-must-every-release-contain
On Thu, Sep 10, 2015 at 11:51 AM, Billie Rinaldi <bi...@gmail.com>
wrote:
> Agreed.
>
> On Thu, Sep 10, 2015 at 9:47 AM, Christopher <ct...@apache.org> wrote:
>
> > I think the license issues are relatively small compared to the bugfixes,
> > especially since we're really trying to close out 1.5.x development. So,
> > given the options, I'd prefer to pass RC1, and make the license fixes in
> > 1.6.x and later, as applicable.
> >
> > On Thu, Sep 10, 2015 at 12:28 PM Josh Elser <el...@apache.org> wrote:
> >
> > > Thanks again for taking the time to inspect things so thoroughly, Sean.
> > >
> > > Others who have already voted, I'd ask for your opinion on whether we
> > > should sink this release (instead of me blindly going by majority
> rule).
> > >
> > > Personally, I'm presently of the opinion that, given the severity of
> the
> > > bug(s) fixed in this release already, RC1 should pass. Considering that
> > > we've been making releases like this for quite some time w/o issue and
> > > 1.5 is all but dead, let's push this release out, (again) table 1.5 and
> > > then make these improvements to 1.6 before we cut an RC there there
> when
> > > we have time to thoroughly vet the changes (instead of the 11th hour of
> > > a vote).
> > >
> > > If there's a need for lengthy discussion, let's break this off the VOTE
> > > thread (I leave this message here for visibility).
> > >
> > > - Josh
> > >
> > > Sean Busbey wrote:
> > > > -1
> > > >
> > > > * signatures check out
> > > > * checksums match
> > > > * licensing errors noted in ACCUMULO-3988
> > > >
> > > > On Sat, Sep 5, 2015 at 4:27 PM, Josh Elser<el...@apache.org>
> wrote:
> > > >
> > > >> Accumulo Developers,
> > > >>
> > > >> Please consider the following candidate for Accumulo 1.5.4.
> > > >>
> > > >> Git Commit:
> > > >> 12a1041dcbb7f3b10543c305f27ece4b0d65ab9c
> > > >> Branch:
> > > >> 1.5.4-rc1
> > > >>
> > > >> If this vote passes, a gpg-signed tag will be created using:
> > > >> git tag -f -m 'Apache Accumulo 1.5.4' -s 1.5.4
> > > >> 12a1041dcbb7f3b10543c305f27ece4b0d65ab9c
> > > >>
> > > >> Staging repo:
> > > >>
> > >
> >
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1039
> > > >> Source (official release artifact):
> > > >>
> > >
> >
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1039/org/apache/accumulo/accumulo/1.5.4/accumulo-1.5.4-src.tar.gz
> > > >> Binary:
> > > >>
> > >
> >
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1039/org/apache/accumulo/accumulo/1.5.4/accumulo-1.5.4-bin.tar.gz
> > > >> (Append ".sha1", ".md5", or ".asc" to download the signature/hash
> for
> > a
> > > >> given artifact.)
> > > >>
> > > >> All artifacts were built and staged with:
> > > >> mvn release:prepare&& mvn release:perform
> > > >>
> > > >> Signing keys are available at
> > https://www.apache.org/dist/accumulo/KEYS
> > > >> (Expected fingerprint: ABC8914C675FAD3FA74F39B2D146D62CAB471AE9)
> > > >>
> > > >> Release notes (in progress) can be found at
> > > >> https://accumulo.apache.org/release_notes/1.5.4
> > > >>
> > > >> Please vote one of:
> > > >> [ ] +1 - I have verified and accept...
> > > >> [ ] +0 - I have reservations, but not strong enough to vote
> against...
> > > >> [ ] -1 - Because..., I do not accept...
> > > >> ... these artifacts as the 1.5.4 release of Apache Accumulo.
> > > >>
> > > >> This vote will end on Thurs Sep 10 23:00:00 UTC 2015
> > > >> (Thurs Sep 10 20:00:00 EDT 2015 / Thurs Sep 10 17:00:00 PDT 2015)
> > > >>
> > > >> Thanks!
> > > >>
> > > >> P.S. Hint: download the whole staging repo with
> > > >> wget -erobots=off -r -l inf -np -nH \
> > > >>
> > > >>
> > >
> >
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1039/
> > > >> # note the trailing slash is needed
> > > >>
> > > >
> > > >
> > > >
> > >
> >
>
--
Sean
Re: [VOTE] Accumulo 1.5.4-rc1
Posted by Billie Rinaldi <bi...@gmail.com>.
Agreed.
On Thu, Sep 10, 2015 at 9:47 AM, Christopher <ct...@apache.org> wrote:
> I think the license issues are relatively small compared to the bugfixes,
> especially since we're really trying to close out 1.5.x development. So,
> given the options, I'd prefer to pass RC1, and make the license fixes in
> 1.6.x and later, as applicable.
>
> On Thu, Sep 10, 2015 at 12:28 PM Josh Elser <el...@apache.org> wrote:
>
> > Thanks again for taking the time to inspect things so thoroughly, Sean.
> >
> > Others who have already voted, I'd ask for your opinion on whether we
> > should sink this release (instead of me blindly going by majority rule).
> >
> > Personally, I'm presently of the opinion that, given the severity of the
> > bug(s) fixed in this release already, RC1 should pass. Considering that
> > we've been making releases like this for quite some time w/o issue and
> > 1.5 is all but dead, let's push this release out, (again) table 1.5 and
> > then make these improvements to 1.6 before we cut an RC there there when
> > we have time to thoroughly vet the changes (instead of the 11th hour of
> > a vote).
> >
> > If there's a need for lengthy discussion, let's break this off the VOTE
> > thread (I leave this message here for visibility).
> >
> > - Josh
> >
> > Sean Busbey wrote:
> > > -1
> > >
> > > * signatures check out
> > > * checksums match
> > > * licensing errors noted in ACCUMULO-3988
> > >
> > > On Sat, Sep 5, 2015 at 4:27 PM, Josh Elser<el...@apache.org> wrote:
> > >
> > >> Accumulo Developers,
> > >>
> > >> Please consider the following candidate for Accumulo 1.5.4.
> > >>
> > >> Git Commit:
> > >> 12a1041dcbb7f3b10543c305f27ece4b0d65ab9c
> > >> Branch:
> > >> 1.5.4-rc1
> > >>
> > >> If this vote passes, a gpg-signed tag will be created using:
> > >> git tag -f -m 'Apache Accumulo 1.5.4' -s 1.5.4
> > >> 12a1041dcbb7f3b10543c305f27ece4b0d65ab9c
> > >>
> > >> Staging repo:
> > >>
> >
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1039
> > >> Source (official release artifact):
> > >>
> >
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1039/org/apache/accumulo/accumulo/1.5.4/accumulo-1.5.4-src.tar.gz
> > >> Binary:
> > >>
> >
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1039/org/apache/accumulo/accumulo/1.5.4/accumulo-1.5.4-bin.tar.gz
> > >> (Append ".sha1", ".md5", or ".asc" to download the signature/hash for
> a
> > >> given artifact.)
> > >>
> > >> All artifacts were built and staged with:
> > >> mvn release:prepare&& mvn release:perform
> > >>
> > >> Signing keys are available at
> https://www.apache.org/dist/accumulo/KEYS
> > >> (Expected fingerprint: ABC8914C675FAD3FA74F39B2D146D62CAB471AE9)
> > >>
> > >> Release notes (in progress) can be found at
> > >> https://accumulo.apache.org/release_notes/1.5.4
> > >>
> > >> Please vote one of:
> > >> [ ] +1 - I have verified and accept...
> > >> [ ] +0 - I have reservations, but not strong enough to vote against...
> > >> [ ] -1 - Because..., I do not accept...
> > >> ... these artifacts as the 1.5.4 release of Apache Accumulo.
> > >>
> > >> This vote will end on Thurs Sep 10 23:00:00 UTC 2015
> > >> (Thurs Sep 10 20:00:00 EDT 2015 / Thurs Sep 10 17:00:00 PDT 2015)
> > >>
> > >> Thanks!
> > >>
> > >> P.S. Hint: download the whole staging repo with
> > >> wget -erobots=off -r -l inf -np -nH \
> > >>
> > >>
> >
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1039/
> > >> # note the trailing slash is needed
> > >>
> > >
> > >
> > >
> >
>
Re: [VOTE] Accumulo 1.5.4-rc1
Posted by Adam Fuchs <af...@apache.org>.
I agree with Chris on this one. I don't see the pre-existing
licensing/copyright notification issue as a blocker to a bugfix release.
Definitely something we should fix as soon as we can, though.
Sorry I can't give a +1 to the release -- I haven't done a thorough enough
review to officially vote.
Adam
On Thu, Sep 10, 2015 at 12:47 PM, Christopher <ct...@apache.org> wrote:
> I think the license issues are relatively small compared to the bugfixes,
> especially since we're really trying to close out 1.5.x development. So,
> given the options, I'd prefer to pass RC1, and make the license fixes in
> 1.6.x and later, as applicable.
>
> On Thu, Sep 10, 2015 at 12:28 PM Josh Elser <el...@apache.org> wrote:
>
> > Thanks again for taking the time to inspect things so thoroughly, Sean.
> >
> > Others who have already voted, I'd ask for your opinion on whether we
> > should sink this release (instead of me blindly going by majority rule).
> >
> > Personally, I'm presently of the opinion that, given the severity of the
> > bug(s) fixed in this release already, RC1 should pass. Considering that
> > we've been making releases like this for quite some time w/o issue and
> > 1.5 is all but dead, let's push this release out, (again) table 1.5 and
> > then make these improvements to 1.6 before we cut an RC there there when
> > we have time to thoroughly vet the changes (instead of the 11th hour of
> > a vote).
> >
> > If there's a need for lengthy discussion, let's break this off the VOTE
> > thread (I leave this message here for visibility).
> >
> > - Josh
> >
> > Sean Busbey wrote:
> > > -1
> > >
> > > * signatures check out
> > > * checksums match
> > > * licensing errors noted in ACCUMULO-3988
> > >
> > > On Sat, Sep 5, 2015 at 4:27 PM, Josh Elser<el...@apache.org> wrote:
> > >
> > >> Accumulo Developers,
> > >>
> > >> Please consider the following candidate for Accumulo 1.5.4.
> > >>
> > >> Git Commit:
> > >> 12a1041dcbb7f3b10543c305f27ece4b0d65ab9c
> > >> Branch:
> > >> 1.5.4-rc1
> > >>
> > >> If this vote passes, a gpg-signed tag will be created using:
> > >> git tag -f -m 'Apache Accumulo 1.5.4' -s 1.5.4
> > >> 12a1041dcbb7f3b10543c305f27ece4b0d65ab9c
> > >>
> > >> Staging repo:
> > >>
> >
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1039
> > >> Source (official release artifact):
> > >>
> >
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1039/org/apache/accumulo/accumulo/1.5.4/accumulo-1.5.4-src.tar.gz
> > >> Binary:
> > >>
> >
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1039/org/apache/accumulo/accumulo/1.5.4/accumulo-1.5.4-bin.tar.gz
> > >> (Append ".sha1", ".md5", or ".asc" to download the signature/hash for
> a
> > >> given artifact.)
> > >>
> > >> All artifacts were built and staged with:
> > >> mvn release:prepare&& mvn release:perform
> > >>
> > >> Signing keys are available at
> https://www.apache.org/dist/accumulo/KEYS
> > >> (Expected fingerprint: ABC8914C675FAD3FA74F39B2D146D62CAB471AE9)
> > >>
> > >> Release notes (in progress) can be found at
> > >> https://accumulo.apache.org/release_notes/1.5.4
> > >>
> > >> Please vote one of:
> > >> [ ] +1 - I have verified and accept...
> > >> [ ] +0 - I have reservations, but not strong enough to vote against...
> > >> [ ] -1 - Because..., I do not accept...
> > >> ... these artifacts as the 1.5.4 release of Apache Accumulo.
> > >>
> > >> This vote will end on Thurs Sep 10 23:00:00 UTC 2015
> > >> (Thurs Sep 10 20:00:00 EDT 2015 / Thurs Sep 10 17:00:00 PDT 2015)
> > >>
> > >> Thanks!
> > >>
> > >> P.S. Hint: download the whole staging repo with
> > >> wget -erobots=off -r -l inf -np -nH \
> > >>
> > >>
> >
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1039/
> > >> # note the trailing slash is needed
> > >>
> > >
> > >
> > >
> >
>
Re: [VOTE] Accumulo 1.5.4-rc1
Posted by Christopher <ct...@apache.org>.
I think the license issues are relatively small compared to the bugfixes,
especially since we're really trying to close out 1.5.x development. So,
given the options, I'd prefer to pass RC1, and make the license fixes in
1.6.x and later, as applicable.
On Thu, Sep 10, 2015 at 12:28 PM Josh Elser <el...@apache.org> wrote:
> Thanks again for taking the time to inspect things so thoroughly, Sean.
>
> Others who have already voted, I'd ask for your opinion on whether we
> should sink this release (instead of me blindly going by majority rule).
>
> Personally, I'm presently of the opinion that, given the severity of the
> bug(s) fixed in this release already, RC1 should pass. Considering that
> we've been making releases like this for quite some time w/o issue and
> 1.5 is all but dead, let's push this release out, (again) table 1.5 and
> then make these improvements to 1.6 before we cut an RC there there when
> we have time to thoroughly vet the changes (instead of the 11th hour of
> a vote).
>
> If there's a need for lengthy discussion, let's break this off the VOTE
> thread (I leave this message here for visibility).
>
> - Josh
>
> Sean Busbey wrote:
> > -1
> >
> > * signatures check out
> > * checksums match
> > * licensing errors noted in ACCUMULO-3988
> >
> > On Sat, Sep 5, 2015 at 4:27 PM, Josh Elser<el...@apache.org> wrote:
> >
> >> Accumulo Developers,
> >>
> >> Please consider the following candidate for Accumulo 1.5.4.
> >>
> >> Git Commit:
> >> 12a1041dcbb7f3b10543c305f27ece4b0d65ab9c
> >> Branch:
> >> 1.5.4-rc1
> >>
> >> If this vote passes, a gpg-signed tag will be created using:
> >> git tag -f -m 'Apache Accumulo 1.5.4' -s 1.5.4
> >> 12a1041dcbb7f3b10543c305f27ece4b0d65ab9c
> >>
> >> Staging repo:
> >>
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1039
> >> Source (official release artifact):
> >>
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1039/org/apache/accumulo/accumulo/1.5.4/accumulo-1.5.4-src.tar.gz
> >> Binary:
> >>
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1039/org/apache/accumulo/accumulo/1.5.4/accumulo-1.5.4-bin.tar.gz
> >> (Append ".sha1", ".md5", or ".asc" to download the signature/hash for a
> >> given artifact.)
> >>
> >> All artifacts were built and staged with:
> >> mvn release:prepare&& mvn release:perform
> >>
> >> Signing keys are available at https://www.apache.org/dist/accumulo/KEYS
> >> (Expected fingerprint: ABC8914C675FAD3FA74F39B2D146D62CAB471AE9)
> >>
> >> Release notes (in progress) can be found at
> >> https://accumulo.apache.org/release_notes/1.5.4
> >>
> >> Please vote one of:
> >> [ ] +1 - I have verified and accept...
> >> [ ] +0 - I have reservations, but not strong enough to vote against...
> >> [ ] -1 - Because..., I do not accept...
> >> ... these artifacts as the 1.5.4 release of Apache Accumulo.
> >>
> >> This vote will end on Thurs Sep 10 23:00:00 UTC 2015
> >> (Thurs Sep 10 20:00:00 EDT 2015 / Thurs Sep 10 17:00:00 PDT 2015)
> >>
> >> Thanks!
> >>
> >> P.S. Hint: download the whole staging repo with
> >> wget -erobots=off -r -l inf -np -nH \
> >>
> >>
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1039/
> >> # note the trailing slash is needed
> >>
> >
> >
> >
>
Re: [VOTE] Accumulo 1.5.4-rc1
Posted by Josh Elser <el...@apache.org>.
Thanks again for taking the time to inspect things so thoroughly, Sean.
Others who have already voted, I'd ask for your opinion on whether we
should sink this release (instead of me blindly going by majority rule).
Personally, I'm presently of the opinion that, given the severity of the
bug(s) fixed in this release already, RC1 should pass. Considering that
we've been making releases like this for quite some time w/o issue and
1.5 is all but dead, let's push this release out, (again) table 1.5 and
then make these improvements to 1.6 before we cut an RC there there when
we have time to thoroughly vet the changes (instead of the 11th hour of
a vote).
If there's a need for lengthy discussion, let's break this off the VOTE
thread (I leave this message here for visibility).
- Josh
Sean Busbey wrote:
> -1
>
> * signatures check out
> * checksums match
> * licensing errors noted in ACCUMULO-3988
>
> On Sat, Sep 5, 2015 at 4:27 PM, Josh Elser<el...@apache.org> wrote:
>
>> Accumulo Developers,
>>
>> Please consider the following candidate for Accumulo 1.5.4.
>>
>> Git Commit:
>> 12a1041dcbb7f3b10543c305f27ece4b0d65ab9c
>> Branch:
>> 1.5.4-rc1
>>
>> If this vote passes, a gpg-signed tag will be created using:
>> git tag -f -m 'Apache Accumulo 1.5.4' -s 1.5.4
>> 12a1041dcbb7f3b10543c305f27ece4b0d65ab9c
>>
>> Staging repo:
>> https://repository.apache.org/content/repositories/orgapacheaccumulo-1039
>> Source (official release artifact):
>> https://repository.apache.org/content/repositories/orgapacheaccumulo-1039/org/apache/accumulo/accumulo/1.5.4/accumulo-1.5.4-src.tar.gz
>> Binary:
>> https://repository.apache.org/content/repositories/orgapacheaccumulo-1039/org/apache/accumulo/accumulo/1.5.4/accumulo-1.5.4-bin.tar.gz
>> (Append ".sha1", ".md5", or ".asc" to download the signature/hash for a
>> given artifact.)
>>
>> All artifacts were built and staged with:
>> mvn release:prepare&& mvn release:perform
>>
>> Signing keys are available at https://www.apache.org/dist/accumulo/KEYS
>> (Expected fingerprint: ABC8914C675FAD3FA74F39B2D146D62CAB471AE9)
>>
>> Release notes (in progress) can be found at
>> https://accumulo.apache.org/release_notes/1.5.4
>>
>> Please vote one of:
>> [ ] +1 - I have verified and accept...
>> [ ] +0 - I have reservations, but not strong enough to vote against...
>> [ ] -1 - Because..., I do not accept...
>> ... these artifacts as the 1.5.4 release of Apache Accumulo.
>>
>> This vote will end on Thurs Sep 10 23:00:00 UTC 2015
>> (Thurs Sep 10 20:00:00 EDT 2015 / Thurs Sep 10 17:00:00 PDT 2015)
>>
>> Thanks!
>>
>> P.S. Hint: download the whole staging repo with
>> wget -erobots=off -r -l inf -np -nH \
>>
>> https://repository.apache.org/content/repositories/orgapacheaccumulo-1039/
>> # note the trailing slash is needed
>>
>
>
>
Re: [VOTE] Accumulo 1.5.4-rc1
Posted by Sean Busbey <bu...@cloudera.com>.
-1
* signatures check out
* checksums match
* licensing errors noted in ACCUMULO-3988
On Sat, Sep 5, 2015 at 4:27 PM, Josh Elser <el...@apache.org> wrote:
> Accumulo Developers,
>
> Please consider the following candidate for Accumulo 1.5.4.
>
> Git Commit:
> 12a1041dcbb7f3b10543c305f27ece4b0d65ab9c
> Branch:
> 1.5.4-rc1
>
> If this vote passes, a gpg-signed tag will be created using:
> git tag -f -m 'Apache Accumulo 1.5.4' -s 1.5.4
> 12a1041dcbb7f3b10543c305f27ece4b0d65ab9c
>
> Staging repo:
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1039
> Source (official release artifact):
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1039/org/apache/accumulo/accumulo/1.5.4/accumulo-1.5.4-src.tar.gz
> Binary:
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1039/org/apache/accumulo/accumulo/1.5.4/accumulo-1.5.4-bin.tar.gz
> (Append ".sha1", ".md5", or ".asc" to download the signature/hash for a
> given artifact.)
>
> All artifacts were built and staged with:
> mvn release:prepare && mvn release:perform
>
> Signing keys are available at https://www.apache.org/dist/accumulo/KEYS
> (Expected fingerprint: ABC8914C675FAD3FA74F39B2D146D62CAB471AE9)
>
> Release notes (in progress) can be found at
> https://accumulo.apache.org/release_notes/1.5.4
>
> Please vote one of:
> [ ] +1 - I have verified and accept...
> [ ] +0 - I have reservations, but not strong enough to vote against...
> [ ] -1 - Because..., I do not accept...
> ... these artifacts as the 1.5.4 release of Apache Accumulo.
>
> This vote will end on Thurs Sep 10 23:00:00 UTC 2015
> (Thurs Sep 10 20:00:00 EDT 2015 / Thurs Sep 10 17:00:00 PDT 2015)
>
> Thanks!
>
> P.S. Hint: download the whole staging repo with
> wget -erobots=off -r -l inf -np -nH \
>
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1039/
> # note the trailing slash is needed
>
--
Sean
Re: [VOTE] Accumulo 1.5.4-rc1
Posted by Christopher <ct...@apache.org>.
+1, I've verified:
* GPG/MD5/SHA1
* RPM GPG sigs
* Built sources/javadocs for each jar
* Jars are sealed
* Jar manifests match git commit
* Source tarball matches checkout of git commit
* Jars match those contained in binary tarball lib directory
* Source tarball builds with `mvn clean verify -Dtimeout.factor=2
-Dhadoop.profile=X` with X=1 and X=2.
On Sat, Sep 5, 2015 at 5:26 PM Josh Elser <el...@apache.org> wrote:
> Accumulo Developers,
>
> Please consider the following candidate for Accumulo 1.5.4.
>
> Git Commit:
> 12a1041dcbb7f3b10543c305f27ece4b0d65ab9c
> Branch:
> 1.5.4-rc1
>
> If this vote passes, a gpg-signed tag will be created using:
> git tag -f -m 'Apache Accumulo 1.5.4' -s 1.5.4
> 12a1041dcbb7f3b10543c305f27ece4b0d65ab9c
>
> Staging repo:
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1039
> Source (official release artifact):
>
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1039/org/apache/accumulo/accumulo/1.5.4/accumulo-1.5.4-src.tar.gz
> Binary:
>
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1039/org/apache/accumulo/accumulo/1.5.4/accumulo-1.5.4-bin.tar.gz
> (Append ".sha1", ".md5", or ".asc" to download the signature/hash for a
> given artifact.)
>
> All artifacts were built and staged with:
> mvn release:prepare && mvn release:perform
>
> Signing keys are available at https://www.apache.org/dist/accumulo/KEYS
> (Expected fingerprint: ABC8914C675FAD3FA74F39B2D146D62CAB471AE9)
>
> Release notes (in progress) can be found at
> https://accumulo.apache.org/release_notes/1.5.4
>
> Please vote one of:
> [ ] +1 - I have verified and accept...
> [ ] +0 - I have reservations, but not strong enough to vote against...
> [ ] -1 - Because..., I do not accept...
> ... these artifacts as the 1.5.4 release of Apache Accumulo.
>
> This vote will end on Thurs Sep 10 23:00:00 UTC 2015
> (Thurs Sep 10 20:00:00 EDT 2015 / Thurs Sep 10 17:00:00 PDT 2015)
>
> Thanks!
>
> P.S. Hint: download the whole staging repo with
> wget -erobots=off -r -l inf -np -nH \
>
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1039/
> # note the trailing slash is needed
>