You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@accumulo.apache.org by Mike Drob <md...@apache.org> on 2016/06/18 04:31:17 UTC
[VOTE] Accumulo 1.7.2-rc2
Accumulo Developers,
Please consider the following candidate for Accumulo 1.7.2.
All content generated via
assemble/build.sh --create-release-candidate -P '!thrift'
Changes from 1.7.2-rc1
ACCUMULO-4346 correct LICENSE file for source to include text of reference
ACCUMULO-4347 Crypto notification should be in README files instead of
NOTICE
Git Commit:
a01e67741d101c3d87f1d6e16d54ff7a96951ad0
Branch:
1.7.2-rc2
If this vote passes, a gpg-signed tag will be created using:
git tag -f -m 'Apache Accumulo 1.7.2' -s rel/1.7.2
a01e67741d101c3d87f1d6e16d54ff7a96951ad0
Staging repo:
https://repository.apache.org/content/repositories/orgapacheaccumulo-1052
Source (official release artifact):
https://repository.apache.org/content/repositories/orgapacheaccumulo-1052/org/apache/accumulo/accumulo/1.7.2/accumulo-1.7.2-src.tar.gz
Binary:
https://repository.apache.org/content/repositories/orgapacheaccumulo-1052/org/apache/accumulo/accumulo/1.7.2/accumulo-1.7.2-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: 86EDB9C33B8517228E88A8F93E48C0C6EF362B9E)
Release notes (in progress) can be found at:
https://accumulo.apache.org/release_notes/1.7.2
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.7.2 release of Apache Accumulo.
This vote will end on Tue Jun 21 05:00:00 UTC 2016
(Tue Jun 21 01:00:00 EDT 2016 / Mon Jun 20 22:00:00 PDT 2016)
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-1052/
# note the trailing slash is needed
Re: [VOTE] Accumulo 1.7.2-rc2
Posted by Christopher <ct...@apache.org>.
Make mine a +1
The discussion for ACCUMULO-4317 seems to be leaning towards adding the fix
in 1.6.6/1.7.3/1.8.0.
On Mon, Jun 20, 2016 at 1:12 PM Christopher <ct...@apache.org> wrote:
> +0
>
> * Verified all hashes, sigs
> * Unit tests and ITs all pass
> (org.apache.accumulo.test.BadDeleteMarkersCreatedIT.test timed out the
> first time, but passed on re-run)
> * Verified contents of bin tarball match jars in staging repo and src
> tarball match rc branch in git
>
> My only concern would be that
> https://issues.apache.org/jira/browse/ACCUMULO-4317 was marked as a
> blocker, but was bumped. So, I'll hold my +1 until it's agreed whether
> that's actually a blocker and should be included in 1.7.2, or if it's not a
> blocker and okay to bump.
>
> On Sat, Jun 18, 2016 at 12:31 AM Mike Drob <md...@apache.org> wrote:
>
>> Accumulo Developers,
>>
>> Please consider the following candidate for Accumulo 1.7.2.
>>
>> All content generated via
>> assemble/build.sh --create-release-candidate -P '!thrift'
>>
>> Changes from 1.7.2-rc1
>>
>> ACCUMULO-4346 correct LICENSE file for source to include text of reference
>> ACCUMULO-4347 Crypto notification should be in README files instead of
>> NOTICE
>>
>> Git Commit:
>> a01e67741d101c3d87f1d6e16d54ff7a96951ad0
>> Branch:
>> 1.7.2-rc2
>>
>> If this vote passes, a gpg-signed tag will be created using:
>> git tag -f -m 'Apache Accumulo 1.7.2' -s rel/1.7.2
>> a01e67741d101c3d87f1d6e16d54ff7a96951ad0
>>
>> Staging repo:
>> https://repository.apache.org/content/repositories/orgapacheaccumulo-1052
>> Source (official release artifact):
>>
>> https://repository.apache.org/content/repositories/orgapacheaccumulo-1052/org/apache/accumulo/accumulo/1.7.2/accumulo-1.7.2-src.tar.gz
>> Binary:
>>
>> https://repository.apache.org/content/repositories/orgapacheaccumulo-1052/org/apache/accumulo/accumulo/1.7.2/accumulo-1.7.2-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: 86EDB9C33B8517228E88A8F93E48C0C6EF362B9E)
>>
>> Release notes (in progress) can be found at:
>> https://accumulo.apache.org/release_notes/1.7.2
>>
>> 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.7.2 release of Apache Accumulo.
>>
>> This vote will end on Tue Jun 21 05:00:00 UTC 2016
>> (Tue Jun 21 01:00:00 EDT 2016 / Mon Jun 20 22:00:00 PDT 2016)
>>
>> 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-1052/
>> # note the trailing slash is needed
>>
>
Re: [VOTE] Accumulo 1.7.2-rc2
Posted by Josh Elser <jo...@gmail.com>.
Christopher wrote:
> +0
>
> * Verified all hashes, sigs
> * Unit tests and ITs all pass
> (org.apache.accumulo.test.BadDeleteMarkersCreatedIT.test timed out the
> first time, but passed on re-run)
> * Verified contents of bin tarball match jars in staging repo and src
> tarball match rc branch in git
>
> My only concern would be that
> https://issues.apache.org/jira/browse/ACCUMULO-4317 was marked as a
> blocker, but was bumped. So, I'll hold my +1 until it's agreed whether
> that's actually a blocker and should be included in 1.7.2, or if it's not a
> blocker and okay to bump.
I'd encourage you to weigh in on how critical you think it is on the
JIRA issue. It seems pretty bad to me that we fail like this, but as
Mike rightfully points out, it isn't a new bug. We failed to get the
patch applied and I think that looks sloppy on our part (I would hate
for someone else to run into the same issue with a 1.7 and still have no
release which contains the fix available).
It's on all of us to decide whether or not the severity of the issue,
not just how I throw my weight around :)
> On Sat, Jun 18, 2016 at 12:31 AM Mike Drob<md...@apache.org> wrote:
>
>> Accumulo Developers,
>>
>> Please consider the following candidate for Accumulo 1.7.2.
>>
>> All content generated via
>> assemble/build.sh --create-release-candidate -P '!thrift'
>>
>> Changes from 1.7.2-rc1
>>
>> ACCUMULO-4346 correct LICENSE file for source to include text of reference
>> ACCUMULO-4347 Crypto notification should be in README files instead of
>> NOTICE
>>
>> Git Commit:
>> a01e67741d101c3d87f1d6e16d54ff7a96951ad0
>> Branch:
>> 1.7.2-rc2
>>
>> If this vote passes, a gpg-signed tag will be created using:
>> git tag -f -m 'Apache Accumulo 1.7.2' -s rel/1.7.2
>> a01e67741d101c3d87f1d6e16d54ff7a96951ad0
>>
>> Staging repo:
>> https://repository.apache.org/content/repositories/orgapacheaccumulo-1052
>> Source (official release artifact):
>>
>> https://repository.apache.org/content/repositories/orgapacheaccumulo-1052/org/apache/accumulo/accumulo/1.7.2/accumulo-1.7.2-src.tar.gz
>> Binary:
>>
>> https://repository.apache.org/content/repositories/orgapacheaccumulo-1052/org/apache/accumulo/accumulo/1.7.2/accumulo-1.7.2-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: 86EDB9C33B8517228E88A8F93E48C0C6EF362B9E)
>>
>> Release notes (in progress) can be found at:
>> https://accumulo.apache.org/release_notes/1.7.2
>>
>> 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.7.2 release of Apache Accumulo.
>>
>> This vote will end on Tue Jun 21 05:00:00 UTC 2016
>> (Tue Jun 21 01:00:00 EDT 2016 / Mon Jun 20 22:00:00 PDT 2016)
>>
>> 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-1052/
>> # note the trailing slash is needed
>>
>
Re: [VOTE] Accumulo 1.7.2-rc2
Posted by Christopher <ct...@apache.org>.
+0
* Verified all hashes, sigs
* Unit tests and ITs all pass
(org.apache.accumulo.test.BadDeleteMarkersCreatedIT.test timed out the
first time, but passed on re-run)
* Verified contents of bin tarball match jars in staging repo and src
tarball match rc branch in git
My only concern would be that
https://issues.apache.org/jira/browse/ACCUMULO-4317 was marked as a
blocker, but was bumped. So, I'll hold my +1 until it's agreed whether
that's actually a blocker and should be included in 1.7.2, or if it's not a
blocker and okay to bump.
On Sat, Jun 18, 2016 at 12:31 AM Mike Drob <md...@apache.org> wrote:
> Accumulo Developers,
>
> Please consider the following candidate for Accumulo 1.7.2.
>
> All content generated via
> assemble/build.sh --create-release-candidate -P '!thrift'
>
> Changes from 1.7.2-rc1
>
> ACCUMULO-4346 correct LICENSE file for source to include text of reference
> ACCUMULO-4347 Crypto notification should be in README files instead of
> NOTICE
>
> Git Commit:
> a01e67741d101c3d87f1d6e16d54ff7a96951ad0
> Branch:
> 1.7.2-rc2
>
> If this vote passes, a gpg-signed tag will be created using:
> git tag -f -m 'Apache Accumulo 1.7.2' -s rel/1.7.2
> a01e67741d101c3d87f1d6e16d54ff7a96951ad0
>
> Staging repo:
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1052
> Source (official release artifact):
>
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1052/org/apache/accumulo/accumulo/1.7.2/accumulo-1.7.2-src.tar.gz
> Binary:
>
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1052/org/apache/accumulo/accumulo/1.7.2/accumulo-1.7.2-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: 86EDB9C33B8517228E88A8F93E48C0C6EF362B9E)
>
> Release notes (in progress) can be found at:
> https://accumulo.apache.org/release_notes/1.7.2
>
> 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.7.2 release of Apache Accumulo.
>
> This vote will end on Tue Jun 21 05:00:00 UTC 2016
> (Tue Jun 21 01:00:00 EDT 2016 / Mon Jun 20 22:00:00 PDT 2016)
>
> 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-1052/
> # note the trailing slash is needed
>
Re: [VOTE] Accumulo 1.7.2-rc2
Posted by Sean Busbey <bu...@cloudera.com>.
+1
* verified checksums and signatures
* source artifact corresponds to referenced commit
* source builds correctly with Oracle JDK 1.7.0_80 / Apache Maven
3.3.9 (including unit tests, not including ITs)
* spot checked LICENSE and NOTICE
On Fri, Jun 17, 2016 at 11:31 PM, Mike Drob <md...@apache.org> wrote:
> Accumulo Developers,
>
> Please consider the following candidate for Accumulo 1.7.2.
>
> All content generated via
> assemble/build.sh --create-release-candidate -P '!thrift'
>
> Changes from 1.7.2-rc1
>
> ACCUMULO-4346 correct LICENSE file for source to include text of reference
> ACCUMULO-4347 Crypto notification should be in README files instead of
> NOTICE
>
> Git Commit:
> a01e67741d101c3d87f1d6e16d54ff7a96951ad0
> Branch:
> 1.7.2-rc2
>
> If this vote passes, a gpg-signed tag will be created using:
> git tag -f -m 'Apache Accumulo 1.7.2' -s rel/1.7.2
> a01e67741d101c3d87f1d6e16d54ff7a96951ad0
>
> Staging repo:
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1052
> Source (official release artifact):
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1052/org/apache/accumulo/accumulo/1.7.2/accumulo-1.7.2-src.tar.gz
> Binary:
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1052/org/apache/accumulo/accumulo/1.7.2/accumulo-1.7.2-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: 86EDB9C33B8517228E88A8F93E48C0C6EF362B9E)
>
> Release notes (in progress) can be found at:
> https://accumulo.apache.org/release_notes/1.7.2
>
> 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.7.2 release of Apache Accumulo.
>
> This vote will end on Tue Jun 21 05:00:00 UTC 2016
> (Tue Jun 21 01:00:00 EDT 2016 / Mon Jun 20 22:00:00 PDT 2016)
>
> 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-1052/
> # note the trailing slash is needed
--
busbey
Re: [VOTE] Accumulo 1.7.2-rc2
Posted by Dylan Hutchison <dh...@cs.washington.edu>.
On Sun, Jun 19, 2016 at 1:07 PM, Josh Elser <jo...@gmail.com> wrote:
>
>
> Dylan Hutchison wrote:
>
>> +1 with notes below~
>>
>> * NOTICE and LICENSE look good to my inexperienced eyes.
>> * Source-compiled binary tar.gz matches the binary tar.gz artifact, except
>> for META-INF entries.
>> * Unit tests pass.
>> * Good checksums and sigs. Fingerprint matches Mike's key.
>> * Graphulo tests pass.
>>
>
> Yay, API compatibility :)
>
> * Sunny integration tests pass on a single-node standalone deployment.
>> Tested on Zookeeper 3.4.6 and both Hadoop 2.4.1 and 2.7.2.
>>
>> Notes / Questions:
>>
>> 1. On the ITs: for some reason I can't figure out, the "stop Accumulo
>> processes" part of ReadWriteIT#sunnyDay gives me trouble when I run it
>> alongside the others, but it passes when I run it alone. Similar
>> story for
>> ExamplesIT#testBulkIngest.
>>
>
> Interesting. Are you setting forkMode > 1? Or running multiple invocations
> of the build at the same time? I wouldn't be surprised if some of the logic
> we have to 'test' is actually wrong when we have concurrent processes
> running, but I'm not sure why these two in particular would have troubles.
>
Nope, I didn't mess with forkMode. In case it helps, here is the command I
use for which the two ITs fail:
mvn verify -P sunny -Daccumulo.it.properties="..." \
-DACCUMULO_CONF_DIR="$ACCUMULO_HOME/conf" -Dhadoop.version=2.7.2
Here is the command for which the two ITs succeed (similar for
ReadWriteIT#sunnyDay):
mvn test-compile failsafe:integration-test failsafe:verify
-Daccumulo.it.properties="..." -Dhadoop.version=2.7.2 \
-Dit.test=ExamplesIT#testBulkIngest -DfailIfNoTests=false
-DACCUMULO_CONF_DIR="$ACCUMULO_HOME/conf"
> 2. On diffing the source-built binary with the binary artifact: it
>> seems
>> the source-built binary has more license information in
>> the META-INF/DEPENDENCIES than the binary artifact, in addition to a
>> few of
>> the entries being permuted. This holds true for all the jars except
>> accumulo-fate.jar. Here is a pastebin for the source-built binary
>> deps
>> <http://pastebin.com/HJZB2See>, and a pastebin for the binary
>> artifact
>> deps<http://pastebin.com/nKfxWd2c> for accumulo-core.jar. Here is
>> a pastebin
>> of their diff<http://pastebin.com/jYtggRLK>. I don't know how
>> significant the difference is; maybe Sean or Christopher could
>> comment.
>>
>
> This is probably due to the difference in the release-process creation of
> the binary tarball and what gets built when you just do a `mvn package` on
> your computer (e.g. activating the 'apache-release' Maven profile). I also
> see findbugs in the list, so that's likely unintended.
>
Indeed I used a different command than the one used for releasing. Mystery
solved. The command I used for this is
mvn clean install -P assemble -P docs -DskipTests -Dfindbugs.skip
-Dhadoop.version="2.7.2"
> Overall, for the purposes of the ASF licensing, the DEPENDENCIES file is a
> "nice to have" (LICENSE and NOTICE are the ones we really need to get
> right).
>
> Also, with your commit bit, you can also use paste.apache.org if you want
> to avoid the ads on pastebin :)
>
> 3. Is it good practice to use a code-signing key with no expiration
>> date?
>>
>
> As I understand it, it's not bad like a non-expiring password, but it's
> good to have an expiration date. If you do lose/compromise your key, at
> least everyone knows that there is a certain date the key is no longer
> valid. It's also easy to extend the validity of your key, IIRC.
>
>
>>
>> On Fri, Jun 17, 2016 at 9:31 PM, Mike Drob<md...@apache.org> wrote:
>>
>> Accumulo Developers,
>>>
>>> Please consider the following candidate for Accumulo 1.7.2.
>>>
>>> All content generated via
>>> assemble/build.sh --create-release-candidate -P '!thrift'
>>>
>>> Changes from 1.7.2-rc1
>>>
>>> ACCUMULO-4346 correct LICENSE file for source to include text of
>>> reference
>>> ACCUMULO-4347 Crypto notification should be in README files instead of
>>> NOTICE
>>>
>>> Git Commit:
>>> a01e67741d101c3d87f1d6e16d54ff7a96951ad0
>>> Branch:
>>> 1.7.2-rc2
>>>
>>> If this vote passes, a gpg-signed tag will be created using:
>>> git tag -f -m 'Apache Accumulo 1.7.2' -s rel/1.7.2
>>> a01e67741d101c3d87f1d6e16d54ff7a96951ad0
>>>
>>> Staging repo:
>>> https://repository.apache.org/content/repositories/orgapacheaccumulo-1052
>>> Source (official release artifact):
>>>
>>>
>>> https://repository.apache.org/content/repositories/orgapacheaccumulo-1052/org/apache/accumulo/accumulo/1.7.2/accumulo-1.7.2-src.tar.gz
>>> Binary:
>>>
>>>
>>> https://repository.apache.org/content/repositories/orgapacheaccumulo-1052/org/apache/accumulo/accumulo/1.7.2/accumulo-1.7.2-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: 86EDB9C33B8517228E88A8F93E48C0C6EF362B9E)
>>>
>>> Release notes (in progress) can be found at:
>>> https://accumulo.apache.org/release_notes/1.7.2
>>>
>>> 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.7.2 release of Apache Accumulo.
>>>
>>> This vote will end on Tue Jun 21 05:00:00 UTC 2016
>>> (Tue Jun 21 01:00:00 EDT 2016 / Mon Jun 20 22:00:00 PDT 2016)
>>>
>>> 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-1052/
>>> # note the trailing slash is needed
>>>
>>>
>>
Re: [VOTE] Accumulo 1.7.2-rc2
Posted by Christopher <ct...@apache.org>.
For what it's worth, the key owner can add or update the expiration date. I
think it's a good idea to expire, and I'd encourage everyone to do so, but
the main thing is to ensure they still have exclusive control of the
private key, and that's hard to prove.
I update my expiration date every few years.
On Sun, Jun 19, 2016, 16:07 Josh Elser <jo...@gmail.com> wrote:
>
>
> Dylan Hutchison wrote:
> > +1 with notes below~
> >
> > * NOTICE and LICENSE look good to my inexperienced eyes.
> > * Source-compiled binary tar.gz matches the binary tar.gz artifact,
> except
> > for META-INF entries.
> > * Unit tests pass.
> > * Good checksums and sigs. Fingerprint matches Mike's key.
> > * Graphulo tests pass.
>
> Yay, API compatibility :)
>
> > * Sunny integration tests pass on a single-node standalone deployment.
> > Tested on Zookeeper 3.4.6 and both Hadoop 2.4.1 and 2.7.2.
> >
> > Notes / Questions:
> >
> > 1. On the ITs: for some reason I can't figure out, the "stop Accumulo
> > processes" part of ReadWriteIT#sunnyDay gives me trouble when I run
> it
> > alongside the others, but it passes when I run it alone. Similar
> story for
> > ExamplesIT#testBulkIngest.
>
> Interesting. Are you setting forkMode > 1? Or running multiple
> invocations of the build at the same time? I wouldn't be surprised if
> some of the logic we have to 'test' is actually wrong when we have
> concurrent processes running, but I'm not sure why these two in
> particular would have troubles.
>
> > 2. On diffing the source-built binary with the binary artifact: it
> seems
> > the source-built binary has more license information in
> > the META-INF/DEPENDENCIES than the binary artifact, in addition to a
> few of
> > the entries being permuted. This holds true for all the jars except
> > accumulo-fate.jar. Here is a pastebin for the source-built binary
> deps
> > <http://pastebin.com/HJZB2See>, and a pastebin for the binary
> artifact
> > deps<http://pastebin.com/nKfxWd2c> for accumulo-core.jar. Here is
> > a pastebin
> > of their diff<http://pastebin.com/jYtggRLK>. I don't know how
> > significant the difference is; maybe Sean or Christopher could
> comment.
>
> This is probably due to the difference in the release-process creation
> of the binary tarball and what gets built when you just do a `mvn
> package` on your computer (e.g. activating the 'apache-release' Maven
> profile). I also see findbugs in the list, so that's likely unintended.
>
> Overall, for the purposes of the ASF licensing, the DEPENDENCIES file is
> a "nice to have" (LICENSE and NOTICE are the ones we really need to get
> right).
>
> Also, with your commit bit, you can also use paste.apache.org if you
> want to avoid the ads on pastebin :)
>
> > 3. Is it good practice to use a code-signing key with no expiration
> date?
>
> As I understand it, it's not bad like a non-expiring password, but it's
> good to have an expiration date. If you do lose/compromise your key, at
> least everyone knows that there is a certain date the key is no longer
> valid. It's also easy to extend the validity of your key, IIRC.
>
> >
> >
> > On Fri, Jun 17, 2016 at 9:31 PM, Mike Drob<md...@apache.org> wrote:
> >
> >> Accumulo Developers,
> >>
> >> Please consider the following candidate for Accumulo 1.7.2.
> >>
> >> All content generated via
> >> assemble/build.sh --create-release-candidate -P '!thrift'
> >>
> >> Changes from 1.7.2-rc1
> >>
> >> ACCUMULO-4346 correct LICENSE file for source to include text of
> reference
> >> ACCUMULO-4347 Crypto notification should be in README files instead of
> >> NOTICE
> >>
> >> Git Commit:
> >> a01e67741d101c3d87f1d6e16d54ff7a96951ad0
> >> Branch:
> >> 1.7.2-rc2
> >>
> >> If this vote passes, a gpg-signed tag will be created using:
> >> git tag -f -m 'Apache Accumulo 1.7.2' -s rel/1.7.2
> >> a01e67741d101c3d87f1d6e16d54ff7a96951ad0
> >>
> >> Staging repo:
> >>
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1052
> >> Source (official release artifact):
> >>
> >>
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1052/org/apache/accumulo/accumulo/1.7.2/accumulo-1.7.2-src.tar.gz
> >> Binary:
> >>
> >>
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1052/org/apache/accumulo/accumulo/1.7.2/accumulo-1.7.2-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: 86EDB9C33B8517228E88A8F93E48C0C6EF362B9E)
> >>
> >> Release notes (in progress) can be found at:
> >> https://accumulo.apache.org/release_notes/1.7.2
> >>
> >> 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.7.2 release of Apache Accumulo.
> >>
> >> This vote will end on Tue Jun 21 05:00:00 UTC 2016
> >> (Tue Jun 21 01:00:00 EDT 2016 / Mon Jun 20 22:00:00 PDT 2016)
> >>
> >> 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-1052/
> >> # note the trailing slash is needed
> >>
> >
>
Re: [VOTE] Accumulo 1.7.2-rc2
Posted by Josh Elser <jo...@gmail.com>.
Dylan Hutchison wrote:
> +1 with notes below~
>
> * NOTICE and LICENSE look good to my inexperienced eyes.
> * Source-compiled binary tar.gz matches the binary tar.gz artifact, except
> for META-INF entries.
> * Unit tests pass.
> * Good checksums and sigs. Fingerprint matches Mike's key.
> * Graphulo tests pass.
Yay, API compatibility :)
> * Sunny integration tests pass on a single-node standalone deployment.
> Tested on Zookeeper 3.4.6 and both Hadoop 2.4.1 and 2.7.2.
>
> Notes / Questions:
>
> 1. On the ITs: for some reason I can't figure out, the "stop Accumulo
> processes" part of ReadWriteIT#sunnyDay gives me trouble when I run it
> alongside the others, but it passes when I run it alone. Similar story for
> ExamplesIT#testBulkIngest.
Interesting. Are you setting forkMode > 1? Or running multiple
invocations of the build at the same time? I wouldn't be surprised if
some of the logic we have to 'test' is actually wrong when we have
concurrent processes running, but I'm not sure why these two in
particular would have troubles.
> 2. On diffing the source-built binary with the binary artifact: it seems
> the source-built binary has more license information in
> the META-INF/DEPENDENCIES than the binary artifact, in addition to a few of
> the entries being permuted. This holds true for all the jars except
> accumulo-fate.jar. Here is a pastebin for the source-built binary deps
> <http://pastebin.com/HJZB2See>, and a pastebin for the binary artifact
> deps<http://pastebin.com/nKfxWd2c> for accumulo-core.jar. Here is
> a pastebin
> of their diff<http://pastebin.com/jYtggRLK>. I don't know how
> significant the difference is; maybe Sean or Christopher could comment.
This is probably due to the difference in the release-process creation
of the binary tarball and what gets built when you just do a `mvn
package` on your computer (e.g. activating the 'apache-release' Maven
profile). I also see findbugs in the list, so that's likely unintended.
Overall, for the purposes of the ASF licensing, the DEPENDENCIES file is
a "nice to have" (LICENSE and NOTICE are the ones we really need to get
right).
Also, with your commit bit, you can also use paste.apache.org if you
want to avoid the ads on pastebin :)
> 3. Is it good practice to use a code-signing key with no expiration date?
As I understand it, it's not bad like a non-expiring password, but it's
good to have an expiration date. If you do lose/compromise your key, at
least everyone knows that there is a certain date the key is no longer
valid. It's also easy to extend the validity of your key, IIRC.
>
>
> On Fri, Jun 17, 2016 at 9:31 PM, Mike Drob<md...@apache.org> wrote:
>
>> Accumulo Developers,
>>
>> Please consider the following candidate for Accumulo 1.7.2.
>>
>> All content generated via
>> assemble/build.sh --create-release-candidate -P '!thrift'
>>
>> Changes from 1.7.2-rc1
>>
>> ACCUMULO-4346 correct LICENSE file for source to include text of reference
>> ACCUMULO-4347 Crypto notification should be in README files instead of
>> NOTICE
>>
>> Git Commit:
>> a01e67741d101c3d87f1d6e16d54ff7a96951ad0
>> Branch:
>> 1.7.2-rc2
>>
>> If this vote passes, a gpg-signed tag will be created using:
>> git tag -f -m 'Apache Accumulo 1.7.2' -s rel/1.7.2
>> a01e67741d101c3d87f1d6e16d54ff7a96951ad0
>>
>> Staging repo:
>> https://repository.apache.org/content/repositories/orgapacheaccumulo-1052
>> Source (official release artifact):
>>
>> https://repository.apache.org/content/repositories/orgapacheaccumulo-1052/org/apache/accumulo/accumulo/1.7.2/accumulo-1.7.2-src.tar.gz
>> Binary:
>>
>> https://repository.apache.org/content/repositories/orgapacheaccumulo-1052/org/apache/accumulo/accumulo/1.7.2/accumulo-1.7.2-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: 86EDB9C33B8517228E88A8F93E48C0C6EF362B9E)
>>
>> Release notes (in progress) can be found at:
>> https://accumulo.apache.org/release_notes/1.7.2
>>
>> 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.7.2 release of Apache Accumulo.
>>
>> This vote will end on Tue Jun 21 05:00:00 UTC 2016
>> (Tue Jun 21 01:00:00 EDT 2016 / Mon Jun 20 22:00:00 PDT 2016)
>>
>> 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-1052/
>> # note the trailing slash is needed
>>
>
Re: [VOTE] Accumulo 1.7.2-rc2
Posted by Dylan Hutchison <dh...@cs.washington.edu>.
+1 with notes below~
* NOTICE and LICENSE look good to my inexperienced eyes.
* Source-compiled binary tar.gz matches the binary tar.gz artifact, except
for META-INF entries.
* Unit tests pass.
* Good checksums and sigs. Fingerprint matches Mike's key.
* Graphulo tests pass.
* Sunny integration tests pass on a single-node standalone deployment.
Tested on Zookeeper 3.4.6 and both Hadoop 2.4.1 and 2.7.2.
Notes / Questions:
1. On the ITs: for some reason I can't figure out, the "stop Accumulo
processes" part of ReadWriteIT#sunnyDay gives me trouble when I run it
alongside the others, but it passes when I run it alone. Similar story for
ExamplesIT#testBulkIngest.
2. On diffing the source-built binary with the binary artifact: it seems
the source-built binary has more license information in
the META-INF/DEPENDENCIES than the binary artifact, in addition to a few of
the entries being permuted. This holds true for all the jars except
accumulo-fate.jar. Here is a pastebin for the source-built binary deps
<http://pastebin.com/HJZB2See>, and a pastebin for the binary artifact
deps <http://pastebin.com/nKfxWd2c> for accumulo-core.jar. Here is
a pastebin
of their diff <http://pastebin.com/jYtggRLK>. I don't know how
significant the difference is; maybe Sean or Christopher could comment.
3. Is it good practice to use a code-signing key with no expiration date?
On Fri, Jun 17, 2016 at 9:31 PM, Mike Drob <md...@apache.org> wrote:
> Accumulo Developers,
>
> Please consider the following candidate for Accumulo 1.7.2.
>
> All content generated via
> assemble/build.sh --create-release-candidate -P '!thrift'
>
> Changes from 1.7.2-rc1
>
> ACCUMULO-4346 correct LICENSE file for source to include text of reference
> ACCUMULO-4347 Crypto notification should be in README files instead of
> NOTICE
>
> Git Commit:
> a01e67741d101c3d87f1d6e16d54ff7a96951ad0
> Branch:
> 1.7.2-rc2
>
> If this vote passes, a gpg-signed tag will be created using:
> git tag -f -m 'Apache Accumulo 1.7.2' -s rel/1.7.2
> a01e67741d101c3d87f1d6e16d54ff7a96951ad0
>
> Staging repo:
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1052
> Source (official release artifact):
>
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1052/org/apache/accumulo/accumulo/1.7.2/accumulo-1.7.2-src.tar.gz
> Binary:
>
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1052/org/apache/accumulo/accumulo/1.7.2/accumulo-1.7.2-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: 86EDB9C33B8517228E88A8F93E48C0C6EF362B9E)
>
> Release notes (in progress) can be found at:
> https://accumulo.apache.org/release_notes/1.7.2
>
> 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.7.2 release of Apache Accumulo.
>
> This vote will end on Tue Jun 21 05:00:00 UTC 2016
> (Tue Jun 21 01:00:00 EDT 2016 / Mon Jun 20 22:00:00 PDT 2016)
>
> 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-1052/
> # note the trailing slash is needed
>
Re: [VOTE] Accumulo 1.7.2-rc2
Posted by Christopher <ct...@apache.org>.
Haven't added up the sum, but my guess is that this vote passed.
Mike has already started working on tagging/publishing artifacts, but ran
into a snag when the wrong branch was unintentionally tagged.
Waiting on INFRA for https://issues.apache.org/jira/browse/INFRA-12153
On Mon, Jun 20, 2016 at 7:58 PM Keith Turner <ke...@deenlo.com> wrote:
> +1
> On Jun 17, 2016 11:31 PM, "Mike Drob" <md...@apache.org> wrote:
>
> > Accumulo Developers,
> >
> > Please consider the following candidate for Accumulo 1.7.2.
> >
> > All content generated via
> > assemble/build.sh --create-release-candidate -P '!thrift'
> >
> > Changes from 1.7.2-rc1
> >
> > ACCUMULO-4346 correct LICENSE file for source to include text of
> reference
> > ACCUMULO-4347 Crypto notification should be in README files instead of
> > NOTICE
> >
> > Git Commit:
> > a01e67741d101c3d87f1d6e16d54ff7a96951ad0
> > Branch:
> > 1.7.2-rc2
> >
> > If this vote passes, a gpg-signed tag will be created using:
> > git tag -f -m 'Apache Accumulo 1.7.2' -s rel/1.7.2
> > a01e67741d101c3d87f1d6e16d54ff7a96951ad0
> >
> > Staging repo:
> >
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1052
> > Source (official release artifact):
> >
> >
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1052/org/apache/accumulo/accumulo/1.7.2/accumulo-1.7.2-src.tar.gz
> > Binary:
> >
> >
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1052/org/apache/accumulo/accumulo/1.7.2/accumulo-1.7.2-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: 86EDB9C33B8517228E88A8F93E48C0C6EF362B9E)
> >
> > Release notes (in progress) can be found at:
> > https://accumulo.apache.org/release_notes/1.7.2
> >
> > 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.7.2 release of Apache Accumulo.
> >
> > This vote will end on Tue Jun 21 05:00:00 UTC 2016
> > (Tue Jun 21 01:00:00 EDT 2016 / Mon Jun 20 22:00:00 PDT 2016)
> >
> > 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-1052/
> > # note the trailing slash is needed
> >
>
Re: [VOTE] Accumulo 1.7.2-rc2
Posted by Keith Turner <ke...@deenlo.com>.
+1
On Jun 17, 2016 11:31 PM, "Mike Drob" <md...@apache.org> wrote:
> Accumulo Developers,
>
> Please consider the following candidate for Accumulo 1.7.2.
>
> All content generated via
> assemble/build.sh --create-release-candidate -P '!thrift'
>
> Changes from 1.7.2-rc1
>
> ACCUMULO-4346 correct LICENSE file for source to include text of reference
> ACCUMULO-4347 Crypto notification should be in README files instead of
> NOTICE
>
> Git Commit:
> a01e67741d101c3d87f1d6e16d54ff7a96951ad0
> Branch:
> 1.7.2-rc2
>
> If this vote passes, a gpg-signed tag will be created using:
> git tag -f -m 'Apache Accumulo 1.7.2' -s rel/1.7.2
> a01e67741d101c3d87f1d6e16d54ff7a96951ad0
>
> Staging repo:
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1052
> Source (official release artifact):
>
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1052/org/apache/accumulo/accumulo/1.7.2/accumulo-1.7.2-src.tar.gz
> Binary:
>
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1052/org/apache/accumulo/accumulo/1.7.2/accumulo-1.7.2-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: 86EDB9C33B8517228E88A8F93E48C0C6EF362B9E)
>
> Release notes (in progress) can be found at:
> https://accumulo.apache.org/release_notes/1.7.2
>
> 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.7.2 release of Apache Accumulo.
>
> This vote will end on Tue Jun 21 05:00:00 UTC 2016
> (Tue Jun 21 01:00:00 EDT 2016 / Mon Jun 20 22:00:00 PDT 2016)
>
> 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-1052/
> # note the trailing slash is needed
>
Re: [VOTE] Accumulo 1.7.2-rc2
Posted by Mike Drob <md...@apache.org>.
Thanks for taking a look, Josh.
Can you give me a little more detail on the NOTICE issue? Why is this
insufficient?
"This product includes software developed at
The Apache Software Foundation (http://www.apache.org/)."
I can see the HTrace NOTICE for the version that we are using
(3.1.0-incubating) here -
https://git-wip-us.apache.org/repos/asf?p=incubator-htrace.git;a=blob;f=NOTICE.txt;h=551cc43630f5088094a5ef7a0f7f43ddbef41345;hb=0cabe569bc05a58c7a319a460eed5e50e136bae7
Do we need to have the full contents included?
Also, I noticed that we have the wrong URL for commons-math in the bin
NOTICE file.
And one more question while we are on this topic -- can we drop the mention
of VFS from the NOTICE file since we have removed the copied code, or do we
still need it because we still maintain a binary dependency?
Thanks,
Mike
On Sun, Jun 19, 2016 at 8:26 PM, Josh Elser <el...@apache.org> wrote:
> -1 (binding)
>
> HTrace's NOTICE is missing in -bin's NOTICE file
>
> """
> htrace-core
> Copyright 2015 The Apache Software Foundation
> """
>
> The good:
>
> * Can run with bin tarball out of the box. Simple write/read/update/read
> works in the shell.
> * `mvn verify -Psunny` passes on src tarball
> * xsums/sigs are fine.
> * Good on you using the long-form keyid
> * Verified no Thrift changes (accounting for the !thrift)
> * Verified no changes to public API code (to avoid running japi)
>
> Sorry, Mike. Wish I could've caught this one on rc1.
>
> - Josh
>
> Mike Drob wrote:
>
>> Accumulo Developers,
>>
>> Please consider the following candidate for Accumulo 1.7.2.
>>
>> All content generated via
>> assemble/build.sh --create-release-candidate -P '!thrift'
>>
>> Changes from 1.7.2-rc1
>>
>> ACCUMULO-4346 correct LICENSE file for source to include text of reference
>> ACCUMULO-4347 Crypto notification should be in README files instead of
>> NOTICE
>>
>> Git Commit:
>> a01e67741d101c3d87f1d6e16d54ff7a96951ad0
>> Branch:
>> 1.7.2-rc2
>>
>> If this vote passes, a gpg-signed tag will be created using:
>> git tag -f -m 'Apache Accumulo 1.7.2' -s rel/1.7.2
>> a01e67741d101c3d87f1d6e16d54ff7a96951ad0
>>
>> Staging repo:
>> https://repository.apache.org/content/repositories/orgapacheaccumulo-1052
>> Source (official release artifact):
>>
>> https://repository.apache.org/content/repositories/orgapacheaccumulo-1052/org/apache/accumulo/accumulo/1.7.2/accumulo-1.7.2-src.tar.gz
>> Binary:
>>
>> https://repository.apache.org/content/repositories/orgapacheaccumulo-1052/org/apache/accumulo/accumulo/1.7.2/accumulo-1.7.2-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: 86EDB9C33B8517228E88A8F93E48C0C6EF362B9E)
>>
>> Release notes (in progress) can be found at:
>> https://accumulo.apache.org/release_notes/1.7.2
>>
>> 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.7.2 release of Apache Accumulo.
>>
>> This vote will end on Tue Jun 21 05:00:00 UTC 2016
>> (Tue Jun 21 01:00:00 EDT 2016 / Mon Jun 20 22:00:00 PDT 2016)
>>
>> 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-1052/
>> # note the trailing slash is needed
>>
>>
Re: [VOTE] Accumulo 1.7.2-rc2
Posted by Josh Elser <el...@apache.org>.
My understanding was that you don't need the "developed at the Apache
Software Foundation" line, but the copyright line was still necessary.
http://www.apache.org/dev/licensing-howto.html#bundle-asf-product
However, I forget about LEGAL-234. It looks like we just dropped the
ball to correct both our NOTICE files and the "licensing howto"
documentation. Thanks for reminding me, Christopher.
This changes my -1 to a +1 (binding). Let's also get issues filed to fix
this stuff before the next release (to avoid this one again).
Mike Drob wrote:
> Ah, I didn't see this response while composing my other one. A similar
> question then, Christopher. Do we need to remove all the individual project
> lines?
>
> On Mon, Jun 20, 2016 at 11:31 AM, Christopher<ct...@apache.org> wrote:
>
>> On Sun, Jun 19, 2016 at 9:26 PM Josh Elser<el...@apache.org> wrote:
>>
>>> -1 (binding)
>>>
>>> HTrace's NOTICE is missing in -bin's NOTICE file
>>>
>>> """
>>> htrace-core
>>> Copyright 2015 The Apache Software Foundation
>>> """
>>>
>>>
>> The NOTICE file should not have entries for other ASF-copyrighted
>> materials. The ones that are there already should not be there. This was
>> discussed on https://issues.apache.org/jira/browse/LEGAL-234 with the
>> conclusion that these were superfluous and the NOTICE could be simplified
>> by omitting these. The fact that these aren't necessary, and the general
>> instructions to omit anything that isn't legally required (
>> http://www.apache.org/dev/licensing-howto.html#mod-notice), means these
>> shouldn't be there.
>>
>> I provide this information in case it changes your vote.
>>
>>
>>> The good:
>>>
>>> * Can run with bin tarball out of the box. Simple write/read/update/read
>>> works in the shell.
>>> * `mvn verify -Psunny` passes on src tarball
>>> * xsums/sigs are fine.
>>> * Good on you using the long-form keyid
>>> * Verified no Thrift changes (accounting for the !thrift)
>>> * Verified no changes to public API code (to avoid running japi)
>>>
>>> Sorry, Mike. Wish I could've caught this one on rc1.
>>>
>>> - Josh
>>>
>>> Mike Drob wrote:
>>>> Accumulo Developers,
>>>>
>>>> Please consider the following candidate for Accumulo 1.7.2.
>>>>
>>>> All content generated via
>>>> assemble/build.sh --create-release-candidate -P '!thrift'
>>>>
>>>> Changes from 1.7.2-rc1
>>>>
>>>> ACCUMULO-4346 correct LICENSE file for source to include text of
>>> reference
>>>> ACCUMULO-4347 Crypto notification should be in README files instead of
>>>> NOTICE
>>>>
>>>> Git Commit:
>>>> a01e67741d101c3d87f1d6e16d54ff7a96951ad0
>>>> Branch:
>>>> 1.7.2-rc2
>>>>
>>>> If this vote passes, a gpg-signed tag will be created using:
>>>> git tag -f -m 'Apache Accumulo 1.7.2' -s rel/1.7.2
>>>> a01e67741d101c3d87f1d6e16d54ff7a96951ad0
>>>>
>>>> Staging repo:
>>>>
>> https://repository.apache.org/content/repositories/orgapacheaccumulo-1052
>>>> Source (official release artifact):
>>>>
>> https://repository.apache.org/content/repositories/orgapacheaccumulo-1052/org/apache/accumulo/accumulo/1.7.2/accumulo-1.7.2-src.tar.gz
>>>> Binary:
>>>>
>> https://repository.apache.org/content/repositories/orgapacheaccumulo-1052/org/apache/accumulo/accumulo/1.7.2/accumulo-1.7.2-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: 86EDB9C33B8517228E88A8F93E48C0C6EF362B9E)
>>>>
>>>> Release notes (in progress) can be found at:
>>>> https://accumulo.apache.org/release_notes/1.7.2
>>>>
>>>> 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.7.2 release of Apache Accumulo.
>>>>
>>>> This vote will end on Tue Jun 21 05:00:00 UTC 2016
>>>> (Tue Jun 21 01:00:00 EDT 2016 / Mon Jun 20 22:00:00 PDT 2016)
>>>>
>>>> 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-1052/
>>>> # note the trailing slash is needed
>>>>
>
Re: [VOTE] Accumulo 1.7.2-rc2
Posted by Christopher <ct...@apache.org>.
I wouldn't consider it a blocker, but yes, I think we should (not all of
them, just the individual ASF projects, which are already covered by the
part you quoted).
On Mon, Jun 20, 2016 at 12:38 PM Mike Drob <md...@mdrob.com> wrote:
> Ah, I didn't see this response while composing my other one. A similar
> question then, Christopher. Do we need to remove all the individual project
> lines?
>
> On Mon, Jun 20, 2016 at 11:31 AM, Christopher <ct...@apache.org> wrote:
>
> > On Sun, Jun 19, 2016 at 9:26 PM Josh Elser <el...@apache.org> wrote:
> >
> > > -1 (binding)
> > >
> > > HTrace's NOTICE is missing in -bin's NOTICE file
> > >
> > > """
> > > htrace-core
> > > Copyright 2015 The Apache Software Foundation
> > > """
> > >
> > >
> > The NOTICE file should not have entries for other ASF-copyrighted
> > materials. The ones that are there already should not be there. This was
> > discussed on https://issues.apache.org/jira/browse/LEGAL-234 with the
> > conclusion that these were superfluous and the NOTICE could be simplified
> > by omitting these. The fact that these aren't necessary, and the general
> > instructions to omit anything that isn't legally required (
> > http://www.apache.org/dev/licensing-howto.html#mod-notice), means these
> > shouldn't be there.
> >
> > I provide this information in case it changes your vote.
> >
> >
> > > The good:
> > >
> > > * Can run with bin tarball out of the box. Simple
> write/read/update/read
> > > works in the shell.
> > > * `mvn verify -Psunny` passes on src tarball
> > > * xsums/sigs are fine.
> > > * Good on you using the long-form keyid
> > > * Verified no Thrift changes (accounting for the !thrift)
> > > * Verified no changes to public API code (to avoid running japi)
> > >
> > > Sorry, Mike. Wish I could've caught this one on rc1.
> > >
> > > - Josh
> > >
> > > Mike Drob wrote:
> > > > Accumulo Developers,
> > > >
> > > > Please consider the following candidate for Accumulo 1.7.2.
> > > >
> > > > All content generated via
> > > > assemble/build.sh --create-release-candidate -P '!thrift'
> > > >
> > > > Changes from 1.7.2-rc1
> > > >
> > > > ACCUMULO-4346 correct LICENSE file for source to include text of
> > > reference
> > > > ACCUMULO-4347 Crypto notification should be in README files instead
> of
> > > > NOTICE
> > > >
> > > > Git Commit:
> > > > a01e67741d101c3d87f1d6e16d54ff7a96951ad0
> > > > Branch:
> > > > 1.7.2-rc2
> > > >
> > > > If this vote passes, a gpg-signed tag will be created using:
> > > > git tag -f -m 'Apache Accumulo 1.7.2' -s rel/1.7.2
> > > > a01e67741d101c3d87f1d6e16d54ff7a96951ad0
> > > >
> > > > Staging repo:
> > > >
> > >
> >
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1052
> > > > Source (official release artifact):
> > > >
> > >
> >
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1052/org/apache/accumulo/accumulo/1.7.2/accumulo-1.7.2-src.tar.gz
> > > > Binary:
> > > >
> > >
> >
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1052/org/apache/accumulo/accumulo/1.7.2/accumulo-1.7.2-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: 86EDB9C33B8517228E88A8F93E48C0C6EF362B9E)
> > > >
> > > > Release notes (in progress) can be found at:
> > > > https://accumulo.apache.org/release_notes/1.7.2
> > > >
> > > > 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.7.2 release of Apache Accumulo.
> > > >
> > > > This vote will end on Tue Jun 21 05:00:00 UTC 2016
> > > > (Tue Jun 21 01:00:00 EDT 2016 / Mon Jun 20 22:00:00 PDT 2016)
> > > >
> > > > 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-1052/
> > > > # note the trailing slash is needed
> > > >
> > >
> >
>
Re: [VOTE] Accumulo 1.7.2-rc2
Posted by Mike Drob <md...@mdrob.com>.
Ah, I didn't see this response while composing my other one. A similar
question then, Christopher. Do we need to remove all the individual project
lines?
On Mon, Jun 20, 2016 at 11:31 AM, Christopher <ct...@apache.org> wrote:
> On Sun, Jun 19, 2016 at 9:26 PM Josh Elser <el...@apache.org> wrote:
>
> > -1 (binding)
> >
> > HTrace's NOTICE is missing in -bin's NOTICE file
> >
> > """
> > htrace-core
> > Copyright 2015 The Apache Software Foundation
> > """
> >
> >
> The NOTICE file should not have entries for other ASF-copyrighted
> materials. The ones that are there already should not be there. This was
> discussed on https://issues.apache.org/jira/browse/LEGAL-234 with the
> conclusion that these were superfluous and the NOTICE could be simplified
> by omitting these. The fact that these aren't necessary, and the general
> instructions to omit anything that isn't legally required (
> http://www.apache.org/dev/licensing-howto.html#mod-notice), means these
> shouldn't be there.
>
> I provide this information in case it changes your vote.
>
>
> > The good:
> >
> > * Can run with bin tarball out of the box. Simple write/read/update/read
> > works in the shell.
> > * `mvn verify -Psunny` passes on src tarball
> > * xsums/sigs are fine.
> > * Good on you using the long-form keyid
> > * Verified no Thrift changes (accounting for the !thrift)
> > * Verified no changes to public API code (to avoid running japi)
> >
> > Sorry, Mike. Wish I could've caught this one on rc1.
> >
> > - Josh
> >
> > Mike Drob wrote:
> > > Accumulo Developers,
> > >
> > > Please consider the following candidate for Accumulo 1.7.2.
> > >
> > > All content generated via
> > > assemble/build.sh --create-release-candidate -P '!thrift'
> > >
> > > Changes from 1.7.2-rc1
> > >
> > > ACCUMULO-4346 correct LICENSE file for source to include text of
> > reference
> > > ACCUMULO-4347 Crypto notification should be in README files instead of
> > > NOTICE
> > >
> > > Git Commit:
> > > a01e67741d101c3d87f1d6e16d54ff7a96951ad0
> > > Branch:
> > > 1.7.2-rc2
> > >
> > > If this vote passes, a gpg-signed tag will be created using:
> > > git tag -f -m 'Apache Accumulo 1.7.2' -s rel/1.7.2
> > > a01e67741d101c3d87f1d6e16d54ff7a96951ad0
> > >
> > > Staging repo:
> > >
> >
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1052
> > > Source (official release artifact):
> > >
> >
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1052/org/apache/accumulo/accumulo/1.7.2/accumulo-1.7.2-src.tar.gz
> > > Binary:
> > >
> >
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1052/org/apache/accumulo/accumulo/1.7.2/accumulo-1.7.2-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: 86EDB9C33B8517228E88A8F93E48C0C6EF362B9E)
> > >
> > > Release notes (in progress) can be found at:
> > > https://accumulo.apache.org/release_notes/1.7.2
> > >
> > > 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.7.2 release of Apache Accumulo.
> > >
> > > This vote will end on Tue Jun 21 05:00:00 UTC 2016
> > > (Tue Jun 21 01:00:00 EDT 2016 / Mon Jun 20 22:00:00 PDT 2016)
> > >
> > > 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-1052/
> > > # note the trailing slash is needed
> > >
> >
>
Re: [VOTE] Accumulo 1.7.2-rc2
Posted by Christopher <ct...@apache.org>.
On Sun, Jun 19, 2016 at 9:26 PM Josh Elser <el...@apache.org> wrote:
> -1 (binding)
>
> HTrace's NOTICE is missing in -bin's NOTICE file
>
> """
> htrace-core
> Copyright 2015 The Apache Software Foundation
> """
>
>
The NOTICE file should not have entries for other ASF-copyrighted
materials. The ones that are there already should not be there. This was
discussed on https://issues.apache.org/jira/browse/LEGAL-234 with the
conclusion that these were superfluous and the NOTICE could be simplified
by omitting these. The fact that these aren't necessary, and the general
instructions to omit anything that isn't legally required (
http://www.apache.org/dev/licensing-howto.html#mod-notice), means these
shouldn't be there.
I provide this information in case it changes your vote.
> The good:
>
> * Can run with bin tarball out of the box. Simple write/read/update/read
> works in the shell.
> * `mvn verify -Psunny` passes on src tarball
> * xsums/sigs are fine.
> * Good on you using the long-form keyid
> * Verified no Thrift changes (accounting for the !thrift)
> * Verified no changes to public API code (to avoid running japi)
>
> Sorry, Mike. Wish I could've caught this one on rc1.
>
> - Josh
>
> Mike Drob wrote:
> > Accumulo Developers,
> >
> > Please consider the following candidate for Accumulo 1.7.2.
> >
> > All content generated via
> > assemble/build.sh --create-release-candidate -P '!thrift'
> >
> > Changes from 1.7.2-rc1
> >
> > ACCUMULO-4346 correct LICENSE file for source to include text of
> reference
> > ACCUMULO-4347 Crypto notification should be in README files instead of
> > NOTICE
> >
> > Git Commit:
> > a01e67741d101c3d87f1d6e16d54ff7a96951ad0
> > Branch:
> > 1.7.2-rc2
> >
> > If this vote passes, a gpg-signed tag will be created using:
> > git tag -f -m 'Apache Accumulo 1.7.2' -s rel/1.7.2
> > a01e67741d101c3d87f1d6e16d54ff7a96951ad0
> >
> > Staging repo:
> >
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1052
> > Source (official release artifact):
> >
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1052/org/apache/accumulo/accumulo/1.7.2/accumulo-1.7.2-src.tar.gz
> > Binary:
> >
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1052/org/apache/accumulo/accumulo/1.7.2/accumulo-1.7.2-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: 86EDB9C33B8517228E88A8F93E48C0C6EF362B9E)
> >
> > Release notes (in progress) can be found at:
> > https://accumulo.apache.org/release_notes/1.7.2
> >
> > 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.7.2 release of Apache Accumulo.
> >
> > This vote will end on Tue Jun 21 05:00:00 UTC 2016
> > (Tue Jun 21 01:00:00 EDT 2016 / Mon Jun 20 22:00:00 PDT 2016)
> >
> > 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-1052/
> > # note the trailing slash is needed
> >
>
Re: [VOTE] Accumulo 1.7.2-rc2
Posted by Josh Elser <jo...@gmail.com>.
I just did a `git log --numstat rel/1.7.1..origin/1.7.2-rc2` and
manually inspected the output. There were only about 30 commits this
time, so it was pretty simple.
Dylan Hutchison wrote:
> Out of curiosity Josh, what tool do you use to verify no public API
> changes, if not japi? I should also read the pom on !thrift.
> On Jun 19, 2016 9:26 PM, "Josh Elser"<el...@apache.org> wrote:
>
> -1 (binding)
>
> HTrace's NOTICE is missing in -bin's NOTICE file
>
> """
> htrace-core
> Copyright 2015 The Apache Software Foundation
> """
>
> The good:
>
> * Can run with bin tarball out of the box. Simple write/read/update/read
> works in the shell.
> * `mvn verify -Psunny` passes on src tarball
> * xsums/sigs are fine.
> * Good on you using the long-form keyid
> * Verified no Thrift changes (accounting for the !thrift)
> * Verified no changes to public API code (to avoid running japi)
>
> Sorry, Mike. Wish I could've caught this one on rc1.
>
> - Josh
>
> Mike Drob wrote:
>
>> Accumulo Developers,
>>
>> Please consider the following candidate for Accumulo 1.7.2.
>>
>> All content generated via
>> assemble/build.sh --create-release-candidate -P '!thrift'
>>
>> Changes from 1.7.2-rc1
>>
>> ACCUMULO-4346 correct LICENSE file for source to include text of reference
>> ACCUMULO-4347 Crypto notification should be in README files instead of
>> NOTICE
>>
>> Git Commit:
>> a01e67741d101c3d87f1d6e16d54ff7a96951ad0
>> Branch:
>> 1.7.2-rc2
>>
>> If this vote passes, a gpg-signed tag will be created using:
>> git tag -f -m 'Apache Accumulo 1.7.2' -s rel/1.7.2
>> a01e67741d101c3d87f1d6e16d54ff7a96951ad0
>>
>> Staging repo:
>> https://repository.apache.org/content/repositories/orgapacheaccumulo-1052
>> Source (official release artifact):
>>
>> https://repository.apache.org/content/repositories/orgapacheaccumulo-1052/org/apache/accumulo/accumulo/1.7.2/accumulo-1.7.2-src.tar.gz
>> Binary:
>>
>> https://repository.apache.org/content/repositories/orgapacheaccumulo-1052/org/apache/accumulo/accumulo/1.7.2/accumulo-1.7.2-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: 86EDB9C33B8517228E88A8F93E48C0C6EF362B9E)
>>
>> Release notes (in progress) can be found at:
>> https://accumulo.apache.org/release_notes/1.7.2
>>
>> 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.7.2 release of Apache Accumulo.
>>
>> This vote will end on Tue Jun 21 05:00:00 UTC 2016
>> (Tue Jun 21 01:00:00 EDT 2016 / Mon Jun 20 22:00:00 PDT 2016)
>>
>> 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-1052/
>> # note the trailing slash is needed
>>
>>
>
Re: [VOTE] Accumulo 1.7.2-rc2
Posted by Dylan Hutchison <dh...@cs.washington.edu>.
Out of curiosity Josh, what tool do you use to verify no public API
changes, if not japi? I should also read the pom on !thrift.
On Jun 19, 2016 9:26 PM, "Josh Elser" <el...@apache.org> wrote:
-1 (binding)
HTrace's NOTICE is missing in -bin's NOTICE file
"""
htrace-core
Copyright 2015 The Apache Software Foundation
"""
The good:
* Can run with bin tarball out of the box. Simple write/read/update/read
works in the shell.
* `mvn verify -Psunny` passes on src tarball
* xsums/sigs are fine.
* Good on you using the long-form keyid
* Verified no Thrift changes (accounting for the !thrift)
* Verified no changes to public API code (to avoid running japi)
Sorry, Mike. Wish I could've caught this one on rc1.
- Josh
Mike Drob wrote:
> Accumulo Developers,
>
> Please consider the following candidate for Accumulo 1.7.2.
>
> All content generated via
> assemble/build.sh --create-release-candidate -P '!thrift'
>
> Changes from 1.7.2-rc1
>
> ACCUMULO-4346 correct LICENSE file for source to include text of reference
> ACCUMULO-4347 Crypto notification should be in README files instead of
> NOTICE
>
> Git Commit:
> a01e67741d101c3d87f1d6e16d54ff7a96951ad0
> Branch:
> 1.7.2-rc2
>
> If this vote passes, a gpg-signed tag will be created using:
> git tag -f -m 'Apache Accumulo 1.7.2' -s rel/1.7.2
> a01e67741d101c3d87f1d6e16d54ff7a96951ad0
>
> Staging repo:
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1052
> Source (official release artifact):
>
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1052/org/apache/accumulo/accumulo/1.7.2/accumulo-1.7.2-src.tar.gz
> Binary:
>
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1052/org/apache/accumulo/accumulo/1.7.2/accumulo-1.7.2-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: 86EDB9C33B8517228E88A8F93E48C0C6EF362B9E)
>
> Release notes (in progress) can be found at:
> https://accumulo.apache.org/release_notes/1.7.2
>
> 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.7.2 release of Apache Accumulo.
>
> This vote will end on Tue Jun 21 05:00:00 UTC 2016
> (Tue Jun 21 01:00:00 EDT 2016 / Mon Jun 20 22:00:00 PDT 2016)
>
> 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-1052/
> # note the trailing slash is needed
>
>
Re: [VOTE] Accumulo 1.7.2-rc2
Posted by Josh Elser <el...@apache.org>.
-1 (binding)
HTrace's NOTICE is missing in -bin's NOTICE file
"""
htrace-core
Copyright 2015 The Apache Software Foundation
"""
The good:
* Can run with bin tarball out of the box. Simple write/read/update/read
works in the shell.
* `mvn verify -Psunny` passes on src tarball
* xsums/sigs are fine.
* Good on you using the long-form keyid
* Verified no Thrift changes (accounting for the !thrift)
* Verified no changes to public API code (to avoid running japi)
Sorry, Mike. Wish I could've caught this one on rc1.
- Josh
Mike Drob wrote:
> Accumulo Developers,
>
> Please consider the following candidate for Accumulo 1.7.2.
>
> All content generated via
> assemble/build.sh --create-release-candidate -P '!thrift'
>
> Changes from 1.7.2-rc1
>
> ACCUMULO-4346 correct LICENSE file for source to include text of reference
> ACCUMULO-4347 Crypto notification should be in README files instead of
> NOTICE
>
> Git Commit:
> a01e67741d101c3d87f1d6e16d54ff7a96951ad0
> Branch:
> 1.7.2-rc2
>
> If this vote passes, a gpg-signed tag will be created using:
> git tag -f -m 'Apache Accumulo 1.7.2' -s rel/1.7.2
> a01e67741d101c3d87f1d6e16d54ff7a96951ad0
>
> Staging repo:
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1052
> Source (official release artifact):
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1052/org/apache/accumulo/accumulo/1.7.2/accumulo-1.7.2-src.tar.gz
> Binary:
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1052/org/apache/accumulo/accumulo/1.7.2/accumulo-1.7.2-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: 86EDB9C33B8517228E88A8F93E48C0C6EF362B9E)
>
> Release notes (in progress) can be found at:
> https://accumulo.apache.org/release_notes/1.7.2
>
> 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.7.2 release of Apache Accumulo.
>
> This vote will end on Tue Jun 21 05:00:00 UTC 2016
> (Tue Jun 21 01:00:00 EDT 2016 / Mon Jun 20 22:00:00 PDT 2016)
>
> 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-1052/
> # note the trailing slash is needed
>