You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@accumulo.apache.org by Christopher <ct...@apache.org> on 2018/04/18 18:58:50 UTC
[RESULT][VOTE] Apache Accumulo 1.9.0-rc1
This vote passes with: 6*(+1) + 1*(-0) + 1*(-1)
+1: edcoleman, mwalch, jmark99, ctubbsii, kturner, mmiller
-0: mdrob
-1: busbey
Thanks for the votes all, I'll start working on the post-vote steps next.
It looks like folks are still making updates to the release notes.
On Wed, Apr 18, 2018 at 2:47 PM Christopher <ct...@apache.org> wrote:
> +1
>
> * Verified SVN staging area (dist/dev/accumulo/1.9.0-rc1) tarballs match
> Nexus staging area (artifacts and GPG sigs) and SHA512s there are correct.
> * Ran mvn verify -DskipTests with both Hadoop 2 and Hadoop 3
> * Ran all ITs successfully with Hadoop 2
> * GPG signatures match release tarball artifacts (and other Maven
> artifacts)
> * Maven repo is consistent (all md5, sha1 sigs match their Maven artifacts)
> * All jars have corresponding javadoc and source jars.
> * Contents of binary tarball lib directory match Maven jars
> * Source tarball matches git commit
> * Jar manifest indicates build from correct git commit
> * Jars are sealed
> * Using 1.9.0 jars, successfully built Apache Fluo (with ITs)|
> * Also attempted to build Hive... which works, but some Accumulo tests
> fail because of the use of "." in iterator names, which is broken, and
> explicitly checked for as of ACCUMULO-3389
> * Also attempted to build geowave, but that failed because geowave appears
> to extensively make use of non-public API from Accumulo, so I gave up.
>
> I checked the LICENSE and NOTICE files also, and they look good, except
> for the fact that they still say 2017, instead of 2018. I can't believe I
> forgot to check this a second time, after this same thing happened for
> 1.7.4. In any case, I don't think it's worth holding up the release, given
> that there do not seem to be any other serious issues with the artifacts.
>
>
> On Wed, Apr 18, 2018 at 11:07 AM Keith Turner <ke...@deenlo.com> wrote:
>
>> +1
>>
>> * Successfully built Fluo against RC
>> * Ran continuous ingest for 24hrs on 9 node cluster using RC.
>> Verified successfully. Table had 32.3 billion entries after test.
>>
>>
>>
>> On Thu, Apr 12, 2018 at 6:21 PM, Christopher <ct...@apache.org> wrote:
>> > Accumulo Developers,
>> >
>> > Please consider the following candidate for Apache Accumulo 1.9.0.
>> >
>> > Git Commit:
>> > bca516000bdb54b1e5582f908e0a525634a120f7
>> > Branch:
>> > 1.9.0-rc1
>> >
>> > If this vote passes, a gpg-signed tag will be created using:
>> > git tag -f -m 'Apache Accumulo 1.9.0' -s rel/1.9.0 \
>> > bca516000bdb54b1e5582f908e0a525634a120f7
>> >
>> > Staging repo:
>> >
>> https://repository.apache.org/content/repositories/orgapacheaccumulo-1070
>> > Source (official release artifact):
>> >
>> https://repository.apache.org/content/repositories/orgapacheaccumulo-1070/org/apache/accumulo/accumulo/1.9.0/accumulo-1.9.0-src.tar.gz
>> > Binary:
>> >
>> https://repository.apache.org/content/repositories/orgapacheaccumulo-1070/org/apache/accumulo/accumulo/1.9.0/accumulo-1.9.0-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: 8CC4F8A2B29C2B040F2B835D6F0CDAE700B6899D)
>> >
>> > Release notes (in progress) can be found at:
>> > https://accumulo.apache.org/release/accumulo-1.9.0/
>> >
>> > 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.9.0 release of Apache Accumulo.
>> >
>> > This vote will remain open until at least Sun Apr 15 22:30:00 UTC 2018
>> > (Sun Apr 15 18:30:00 EDT 2018 / Sun Apr 15 15:30:00 PDT 2018).
>> > Voting continues until the release manager sends an email closing the
>> vote.
>> >
>> > 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-1070/
>> > # note the trailing slash is needed
>>
>
Re: [RESULT][VOTE] Apache Accumulo 1.9.0-rc1
Posted by Christopher <ct...@apache.org>.
#440 (add SHA512 sums to vote generated vote email) and #433 (bump
copyright year) wraps up all these tasks. Please provide any feedback if
you think additional changes need to be made to the release process.
On Tue, Apr 24, 2018 at 6:01 PM Christopher <ct...@apache.org> wrote:
> Completed all these steps, except for updating the build.sh script to
> include the SHA512 sums... which I'm working on.
>
> On Wed, Apr 18, 2018 at 7:45 PM Christopher <ct...@apache.org> wrote:
>
>> Post-vote steps I've completed:
>>
>> 1. svn mv from dist/dev area to dist/release
>> 2. Release staged Maven repository
>> 3. Sign and push git tag
>> 4. Merge in and clean up git branches
>> 5. Added release date to reporter.apache.org
>> 6. Cleaned up JIRA version for 1.9.0
>> 7. Update Jenkins jobs for 1.9 instead of 1.8 branch
>>
>> (NOTE: I renamed the 1.8 branch to 1.9 as part of item 4)
>>
>> Stuff to do tomorrow:
>>
>> 1. Publish release notes
>> 2. Update downloads page
>> 3. Update website with docs/examples/javadocs
>> 4. Update DOAP
>> 5. Announce the release
>> 6. Tweet about release
>>
>> Stuff to do after that:
>>
>> 1. Update build.sh script as previously discussed
>> 2. Update copyright year for next releases (
>> https://github.com/apache/accumulo/issues/433)
>>
>>
>> On Wed, Apr 18, 2018 at 2:58 PM Christopher <ct...@apache.org> wrote:
>>
>>> This vote passes with: 6*(+1) + 1*(-0) + 1*(-1)
>>>
>>> +1: edcoleman, mwalch, jmark99, ctubbsii, kturner, mmiller
>>> -0: mdrob
>>> -1: busbey
>>>
>>> Thanks for the votes all, I'll start working on the post-vote steps
>>> next. It looks like folks are still making updates to the release notes.
>>>
>>> On Wed, Apr 18, 2018 at 2:47 PM Christopher <ct...@apache.org> wrote:
>>>
>>>> +1
>>>>
>>>> * Verified SVN staging area (dist/dev/accumulo/1.9.0-rc1) tarballs
>>>> match Nexus staging area (artifacts and GPG sigs) and SHA512s there are
>>>> correct.
>>>> * Ran mvn verify -DskipTests with both Hadoop 2 and Hadoop 3
>>>> * Ran all ITs successfully with Hadoop 2
>>>> * GPG signatures match release tarball artifacts (and other Maven
>>>> artifacts)
>>>> * Maven repo is consistent (all md5, sha1 sigs match their Maven
>>>> artifacts)
>>>> * All jars have corresponding javadoc and source jars.
>>>> * Contents of binary tarball lib directory match Maven jars
>>>> * Source tarball matches git commit
>>>> * Jar manifest indicates build from correct git commit
>>>> * Jars are sealed
>>>> * Using 1.9.0 jars, successfully built Apache Fluo (with ITs)|
>>>> * Also attempted to build Hive... which works, but some Accumulo tests
>>>> fail because of the use of "." in iterator names, which is broken, and
>>>> explicitly checked for as of ACCUMULO-3389
>>>> * Also attempted to build geowave, but that failed because geowave
>>>> appears to extensively make use of non-public API from Accumulo, so I gave
>>>> up.
>>>>
>>>> I checked the LICENSE and NOTICE files also, and they look good, except
>>>> for the fact that they still say 2017, instead of 2018. I can't believe I
>>>> forgot to check this a second time, after this same thing happened for
>>>> 1.7.4. In any case, I don't think it's worth holding up the release, given
>>>> that there do not seem to be any other serious issues with the artifacts.
>>>>
>>>>
>>>> On Wed, Apr 18, 2018 at 11:07 AM Keith Turner <ke...@deenlo.com> wrote:
>>>>
>>>>> +1
>>>>>
>>>>> * Successfully built Fluo against RC
>>>>> * Ran continuous ingest for 24hrs on 9 node cluster using RC.
>>>>> Verified successfully. Table had 32.3 billion entries after test.
>>>>>
>>>>>
>>>>>
>>>>> On Thu, Apr 12, 2018 at 6:21 PM, Christopher <ct...@apache.org>
>>>>> wrote:
>>>>> > Accumulo Developers,
>>>>> >
>>>>> > Please consider the following candidate for Apache Accumulo 1.9.0.
>>>>> >
>>>>> > Git Commit:
>>>>> > bca516000bdb54b1e5582f908e0a525634a120f7
>>>>> > Branch:
>>>>> > 1.9.0-rc1
>>>>> >
>>>>> > If this vote passes, a gpg-signed tag will be created using:
>>>>> > git tag -f -m 'Apache Accumulo 1.9.0' -s rel/1.9.0 \
>>>>> > bca516000bdb54b1e5582f908e0a525634a120f7
>>>>> >
>>>>> > Staging repo:
>>>>> >
>>>>> https://repository.apache.org/content/repositories/orgapacheaccumulo-1070
>>>>> > Source (official release artifact):
>>>>> >
>>>>> https://repository.apache.org/content/repositories/orgapacheaccumulo-1070/org/apache/accumulo/accumulo/1.9.0/accumulo-1.9.0-src.tar.gz
>>>>> > Binary:
>>>>> >
>>>>> https://repository.apache.org/content/repositories/orgapacheaccumulo-1070/org/apache/accumulo/accumulo/1.9.0/accumulo-1.9.0-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: 8CC4F8A2B29C2B040F2B835D6F0CDAE700B6899D)
>>>>> >
>>>>> > Release notes (in progress) can be found at:
>>>>> > https://accumulo.apache.org/release/accumulo-1.9.0/
>>>>> >
>>>>> > 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.9.0 release of Apache Accumulo.
>>>>> >
>>>>> > This vote will remain open until at least Sun Apr 15 22:30:00 UTC
>>>>> 2018
>>>>> > (Sun Apr 15 18:30:00 EDT 2018 / Sun Apr 15 15:30:00 PDT 2018).
>>>>> > Voting continues until the release manager sends an email closing
>>>>> the vote.
>>>>> >
>>>>> > 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-1070/
>>>>> > # note the trailing slash is needed
>>>>>
>>>>
Re: [RESULT][VOTE] Apache Accumulo 1.9.0-rc1
Posted by Christopher <ct...@apache.org>.
Completed all these steps, except for updating the build.sh script to
include the SHA512 sums... which I'm working on.
On Wed, Apr 18, 2018 at 7:45 PM Christopher <ct...@apache.org> wrote:
> Post-vote steps I've completed:
>
> 1. svn mv from dist/dev area to dist/release
> 2. Release staged Maven repository
> 3. Sign and push git tag
> 4. Merge in and clean up git branches
> 5. Added release date to reporter.apache.org
> 6. Cleaned up JIRA version for 1.9.0
> 7. Update Jenkins jobs for 1.9 instead of 1.8 branch
>
> (NOTE: I renamed the 1.8 branch to 1.9 as part of item 4)
>
> Stuff to do tomorrow:
>
> 1. Publish release notes
> 2. Update downloads page
> 3. Update website with docs/examples/javadocs
> 4. Update DOAP
> 5. Announce the release
> 6. Tweet about release
>
> Stuff to do after that:
>
> 1. Update build.sh script as previously discussed
> 2. Update copyright year for next releases (
> https://github.com/apache/accumulo/issues/433)
>
>
> On Wed, Apr 18, 2018 at 2:58 PM Christopher <ct...@apache.org> wrote:
>
>> This vote passes with: 6*(+1) + 1*(-0) + 1*(-1)
>>
>> +1: edcoleman, mwalch, jmark99, ctubbsii, kturner, mmiller
>> -0: mdrob
>> -1: busbey
>>
>> Thanks for the votes all, I'll start working on the post-vote steps next.
>> It looks like folks are still making updates to the release notes.
>>
>> On Wed, Apr 18, 2018 at 2:47 PM Christopher <ct...@apache.org> wrote:
>>
>>> +1
>>>
>>> * Verified SVN staging area (dist/dev/accumulo/1.9.0-rc1) tarballs match
>>> Nexus staging area (artifacts and GPG sigs) and SHA512s there are correct.
>>> * Ran mvn verify -DskipTests with both Hadoop 2 and Hadoop 3
>>> * Ran all ITs successfully with Hadoop 2
>>> * GPG signatures match release tarball artifacts (and other Maven
>>> artifacts)
>>> * Maven repo is consistent (all md5, sha1 sigs match their Maven
>>> artifacts)
>>> * All jars have corresponding javadoc and source jars.
>>> * Contents of binary tarball lib directory match Maven jars
>>> * Source tarball matches git commit
>>> * Jar manifest indicates build from correct git commit
>>> * Jars are sealed
>>> * Using 1.9.0 jars, successfully built Apache Fluo (with ITs)|
>>> * Also attempted to build Hive... which works, but some Accumulo tests
>>> fail because of the use of "." in iterator names, which is broken, and
>>> explicitly checked for as of ACCUMULO-3389
>>> * Also attempted to build geowave, but that failed because geowave
>>> appears to extensively make use of non-public API from Accumulo, so I gave
>>> up.
>>>
>>> I checked the LICENSE and NOTICE files also, and they look good, except
>>> for the fact that they still say 2017, instead of 2018. I can't believe I
>>> forgot to check this a second time, after this same thing happened for
>>> 1.7.4. In any case, I don't think it's worth holding up the release, given
>>> that there do not seem to be any other serious issues with the artifacts.
>>>
>>>
>>> On Wed, Apr 18, 2018 at 11:07 AM Keith Turner <ke...@deenlo.com> wrote:
>>>
>>>> +1
>>>>
>>>> * Successfully built Fluo against RC
>>>> * Ran continuous ingest for 24hrs on 9 node cluster using RC.
>>>> Verified successfully. Table had 32.3 billion entries after test.
>>>>
>>>>
>>>>
>>>> On Thu, Apr 12, 2018 at 6:21 PM, Christopher <ct...@apache.org>
>>>> wrote:
>>>> > Accumulo Developers,
>>>> >
>>>> > Please consider the following candidate for Apache Accumulo 1.9.0.
>>>> >
>>>> > Git Commit:
>>>> > bca516000bdb54b1e5582f908e0a525634a120f7
>>>> > Branch:
>>>> > 1.9.0-rc1
>>>> >
>>>> > If this vote passes, a gpg-signed tag will be created using:
>>>> > git tag -f -m 'Apache Accumulo 1.9.0' -s rel/1.9.0 \
>>>> > bca516000bdb54b1e5582f908e0a525634a120f7
>>>> >
>>>> > Staging repo:
>>>> >
>>>> https://repository.apache.org/content/repositories/orgapacheaccumulo-1070
>>>> > Source (official release artifact):
>>>> >
>>>> https://repository.apache.org/content/repositories/orgapacheaccumulo-1070/org/apache/accumulo/accumulo/1.9.0/accumulo-1.9.0-src.tar.gz
>>>> > Binary:
>>>> >
>>>> https://repository.apache.org/content/repositories/orgapacheaccumulo-1070/org/apache/accumulo/accumulo/1.9.0/accumulo-1.9.0-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: 8CC4F8A2B29C2B040F2B835D6F0CDAE700B6899D)
>>>> >
>>>> > Release notes (in progress) can be found at:
>>>> > https://accumulo.apache.org/release/accumulo-1.9.0/
>>>> >
>>>> > 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.9.0 release of Apache Accumulo.
>>>> >
>>>> > This vote will remain open until at least Sun Apr 15 22:30:00 UTC 2018
>>>> > (Sun Apr 15 18:30:00 EDT 2018 / Sun Apr 15 15:30:00 PDT 2018).
>>>> > Voting continues until the release manager sends an email closing the
>>>> vote.
>>>> >
>>>> > 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-1070/
>>>> > # note the trailing slash is needed
>>>>
>>>
Re: [RESULT][VOTE] Apache Accumulo 1.9.0-rc1
Posted by Christopher <ct...@apache.org>.
Post-vote steps I've completed:
1. svn mv from dist/dev area to dist/release
2. Release staged Maven repository
3. Sign and push git tag
4. Merge in and clean up git branches
5. Added release date to reporter.apache.org
6. Cleaned up JIRA version for 1.9.0
7. Update Jenkins jobs for 1.9 instead of 1.8 branch
(NOTE: I renamed the 1.8 branch to 1.9 as part of item 4)
Stuff to do tomorrow:
1. Publish release notes
2. Update downloads page
3. Update website with docs/examples/javadocs
4. Update DOAP
5. Announce the release
6. Tweet about release
Stuff to do after that:
1. Update build.sh script as previously discussed
2. Update copyright year for next releases (
https://github.com/apache/accumulo/issues/433)
On Wed, Apr 18, 2018 at 2:58 PM Christopher <ct...@apache.org> wrote:
> This vote passes with: 6*(+1) + 1*(-0) + 1*(-1)
>
> +1: edcoleman, mwalch, jmark99, ctubbsii, kturner, mmiller
> -0: mdrob
> -1: busbey
>
> Thanks for the votes all, I'll start working on the post-vote steps next.
> It looks like folks are still making updates to the release notes.
>
> On Wed, Apr 18, 2018 at 2:47 PM Christopher <ct...@apache.org> wrote:
>
>> +1
>>
>> * Verified SVN staging area (dist/dev/accumulo/1.9.0-rc1) tarballs match
>> Nexus staging area (artifacts and GPG sigs) and SHA512s there are correct.
>> * Ran mvn verify -DskipTests with both Hadoop 2 and Hadoop 3
>> * Ran all ITs successfully with Hadoop 2
>> * GPG signatures match release tarball artifacts (and other Maven
>> artifacts)
>> * Maven repo is consistent (all md5, sha1 sigs match their Maven
>> artifacts)
>> * All jars have corresponding javadoc and source jars.
>> * Contents of binary tarball lib directory match Maven jars
>> * Source tarball matches git commit
>> * Jar manifest indicates build from correct git commit
>> * Jars are sealed
>> * Using 1.9.0 jars, successfully built Apache Fluo (with ITs)|
>> * Also attempted to build Hive... which works, but some Accumulo tests
>> fail because of the use of "." in iterator names, which is broken, and
>> explicitly checked for as of ACCUMULO-3389
>> * Also attempted to build geowave, but that failed because geowave
>> appears to extensively make use of non-public API from Accumulo, so I gave
>> up.
>>
>> I checked the LICENSE and NOTICE files also, and they look good, except
>> for the fact that they still say 2017, instead of 2018. I can't believe I
>> forgot to check this a second time, after this same thing happened for
>> 1.7.4. In any case, I don't think it's worth holding up the release, given
>> that there do not seem to be any other serious issues with the artifacts.
>>
>>
>> On Wed, Apr 18, 2018 at 11:07 AM Keith Turner <ke...@deenlo.com> wrote:
>>
>>> +1
>>>
>>> * Successfully built Fluo against RC
>>> * Ran continuous ingest for 24hrs on 9 node cluster using RC.
>>> Verified successfully. Table had 32.3 billion entries after test.
>>>
>>>
>>>
>>> On Thu, Apr 12, 2018 at 6:21 PM, Christopher <ct...@apache.org>
>>> wrote:
>>> > Accumulo Developers,
>>> >
>>> > Please consider the following candidate for Apache Accumulo 1.9.0.
>>> >
>>> > Git Commit:
>>> > bca516000bdb54b1e5582f908e0a525634a120f7
>>> > Branch:
>>> > 1.9.0-rc1
>>> >
>>> > If this vote passes, a gpg-signed tag will be created using:
>>> > git tag -f -m 'Apache Accumulo 1.9.0' -s rel/1.9.0 \
>>> > bca516000bdb54b1e5582f908e0a525634a120f7
>>> >
>>> > Staging repo:
>>> >
>>> https://repository.apache.org/content/repositories/orgapacheaccumulo-1070
>>> > Source (official release artifact):
>>> >
>>> https://repository.apache.org/content/repositories/orgapacheaccumulo-1070/org/apache/accumulo/accumulo/1.9.0/accumulo-1.9.0-src.tar.gz
>>> > Binary:
>>> >
>>> https://repository.apache.org/content/repositories/orgapacheaccumulo-1070/org/apache/accumulo/accumulo/1.9.0/accumulo-1.9.0-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: 8CC4F8A2B29C2B040F2B835D6F0CDAE700B6899D)
>>> >
>>> > Release notes (in progress) can be found at:
>>> > https://accumulo.apache.org/release/accumulo-1.9.0/
>>> >
>>> > 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.9.0 release of Apache Accumulo.
>>> >
>>> > This vote will remain open until at least Sun Apr 15 22:30:00 UTC 2018
>>> > (Sun Apr 15 18:30:00 EDT 2018 / Sun Apr 15 15:30:00 PDT 2018).
>>> > Voting continues until the release manager sends an email closing the
>>> vote.
>>> >
>>> > 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-1070/
>>> > # note the trailing slash is needed
>>>
>>
Re: [RESULT][VOTE] Apache Accumulo 1.9.0-rc1
Posted by Christopher <ct...@apache.org>.
On Wed, Apr 18, 2018 at 5:12 PM Sean Busbey <bu...@cloudera.com> wrote:
> On Wed, Apr 18, 2018 at 3:02 PM, Christopher <ct...@apache.org> wrote:
>
> >
> >
> > In response to Sean and Mike's comments, I copied the tarballs to the SVN
> > dist/dev area, along with their SHA512 sums, but no votes were changed
> as a
> > result. I saw no indication in the discussion that anybody other than
> > myself examined those files to ensure they met expectations. I also
> > proposed a change in the thread to the release process as a result of
> Sean
> > and Mike's comments (specifically, to include the SHA512 for the
> tarballs,
> > directly in future vote threads), but have not heard a response back on
> > that proposal. I will likely proceed with a change to the build.sh script
> > to incorporate that proposal in a future pull request, unless somebody
> has
> > a better proposal before then.
> >
> >
> Sorry, didn't realize this bit was waiting for a response. Including the
> SHA512 in the VOTE thread for the RC satisfies my request, IMO.
>
>
I wasn't necessarily awaiting a response. I was only documenting for Mike
the current status that no response had occurred...yet).
Nevertheless, the response is helpful. Thanks :)
Re: [RESULT][VOTE] Apache Accumulo 1.9.0-rc1
Posted by Sean Busbey <bu...@cloudera.com>.
On Wed, Apr 18, 2018 at 3:02 PM, Christopher <ct...@apache.org> wrote:
>
>
> In response to Sean and Mike's comments, I copied the tarballs to the SVN
> dist/dev area, along with their SHA512 sums, but no votes were changed as a
> result. I saw no indication in the discussion that anybody other than
> myself examined those files to ensure they met expectations. I also
> proposed a change in the thread to the release process as a result of Sean
> and Mike's comments (specifically, to include the SHA512 for the tarballs,
> directly in future vote threads), but have not heard a response back on
> that proposal. I will likely proceed with a change to the build.sh script
> to incorporate that proposal in a future pull request, unless somebody has
> a better proposal before then.
>
>
Sorry, didn't realize this bit was waiting for a response. Including the
SHA512 in the VOTE thread for the RC satisfies my request, IMO.
--
busbey
Re: [RESULT][VOTE] Apache Accumulo 1.9.0-rc1
Posted by Michael Wall <mj...@gmail.com>.
Thanks for the summary Christopher, and thanks for pushing the release
through.
On Wed, Apr 18, 2018 at 4:02 PM Christopher <ct...@apache.org> wrote:
> On Wed, Apr 18, 2018 at 3:21 PM Michael Wall <mj...@gmail.com> wrote:
>
> > Congrats. Don't forget to update the release notes with the testing
> > information to include versions. I didn't realize that 1.9 would work
> with
> > Hadoop 3 but I see it in the parent pom as a profile. Also, did anything
> > change as result of Sean and Mike's comments?
> >
> >
> Regarding Hadoop 3 and testing,
>
> Accumulo 1.9.0 will, in theory, work with Hadoop 3, because of the work
> Josh did to check during development, and to modify the build... but using
> it with Hadoop 3 may require building from source with the Hadoop 3
> profile, or at least, require users to perform some packaging/integration
> steps to set up the class path for their deployments with Hadoop 3. I don't
> know if anybody has done any tests other than build tests with the profile
> active. Also, some Hadoop 3 features may or may not be available, due to
> lack of Accumulo ability to configure them (per-table HDFS erasure encoding
> settings, for example, as an alternative to replication factor). In short,
> user mileage may vary, but at least the option is there to try (because the
> code compiles and the basic build tests pass).
>
> Regarding Sean and Mike's comments:
>
> In response to Sean and Mike's comments, I copied the tarballs to the SVN
> dist/dev area, along with their SHA512 sums, but no votes were changed as a
> result. I saw no indication in the discussion that anybody other than
> myself examined those files to ensure they met expectations. I also
> proposed a change in the thread to the release process as a result of Sean
> and Mike's comments (specifically, to include the SHA512 for the tarballs,
> directly in future vote threads), but have not heard a response back on
> that proposal. I will likely proceed with a change to the build.sh script
> to incorporate that proposal in a future pull request, unless somebody has
> a better proposal before then.
>
>
>
> > On Wed, Apr 18, 2018 at 2:59 PM Christopher <ct...@apache.org> wrote:
> >
> > > This vote passes with: 6*(+1) + 1*(-0) + 1*(-1)
> > >
> > > +1: edcoleman, mwalch, jmark99, ctubbsii, kturner, mmiller
> > > -0: mdrob
> > > -1: busbey
> > >
> > > Thanks for the votes all, I'll start working on the post-vote steps
> next.
> > > It looks like folks are still making updates to the release notes.
> > >
> > > On Wed, Apr 18, 2018 at 2:47 PM Christopher <ct...@apache.org>
> wrote:
> > >
> > > > +1
> > > >
> > > > * Verified SVN staging area (dist/dev/accumulo/1.9.0-rc1) tarballs
> > match
> > > > Nexus staging area (artifacts and GPG sigs) and SHA512s there are
> > > correct.
> > > > * Ran mvn verify -DskipTests with both Hadoop 2 and Hadoop 3
> > > > * Ran all ITs successfully with Hadoop 2
> > > > * GPG signatures match release tarball artifacts (and other Maven
> > > > artifacts)
> > > > * Maven repo is consistent (all md5, sha1 sigs match their Maven
> > > artifacts)
> > > > * All jars have corresponding javadoc and source jars.
> > > > * Contents of binary tarball lib directory match Maven jars
> > > > * Source tarball matches git commit
> > > > * Jar manifest indicates build from correct git commit
> > > > * Jars are sealed
> > > > * Using 1.9.0 jars, successfully built Apache Fluo (with ITs)|
> > > > * Also attempted to build Hive... which works, but some Accumulo
> tests
> > > > fail because of the use of "." in iterator names, which is broken,
> and
> > > > explicitly checked for as of ACCUMULO-3389
> > > > * Also attempted to build geowave, but that failed because geowave
> > > appears
> > > > to extensively make use of non-public API from Accumulo, so I gave
> up.
> > > >
> > > > I checked the LICENSE and NOTICE files also, and they look good,
> except
> > > > for the fact that they still say 2017, instead of 2018. I can't
> > believe I
> > > > forgot to check this a second time, after this same thing happened
> for
> > > > 1.7.4. In any case, I don't think it's worth holding up the release,
> > > given
> > > > that there do not seem to be any other serious issues with the
> > artifacts.
> > > >
> > > >
> > > > On Wed, Apr 18, 2018 at 11:07 AM Keith Turner <ke...@deenlo.com>
> > wrote:
> > > >
> > > >> +1
> > > >>
> > > >> * Successfully built Fluo against RC
> > > >> * Ran continuous ingest for 24hrs on 9 node cluster using RC.
> > > >> Verified successfully. Table had 32.3 billion entries after test.
> > > >>
> > > >>
> > > >>
> > > >> On Thu, Apr 12, 2018 at 6:21 PM, Christopher <ct...@apache.org>
> > > wrote:
> > > >> > Accumulo Developers,
> > > >> >
> > > >> > Please consider the following candidate for Apache Accumulo 1.9.0.
> > > >> >
> > > >> > Git Commit:
> > > >> > bca516000bdb54b1e5582f908e0a525634a120f7
> > > >> > Branch:
> > > >> > 1.9.0-rc1
> > > >> >
> > > >> > If this vote passes, a gpg-signed tag will be created using:
> > > >> > git tag -f -m 'Apache Accumulo 1.9.0' -s rel/1.9.0 \
> > > >> > bca516000bdb54b1e5582f908e0a525634a120f7
> > > >> >
> > > >> > Staging repo:
> > > >> >
> > > >>
> > >
> >
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1070
> > > >> > Source (official release artifact):
> > > >> >
> > > >>
> > >
> >
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1070/org/apache/accumulo/accumulo/1.9.0/accumulo-1.9.0-src.tar.gz
> > > >> > Binary:
> > > >> >
> > > >>
> > >
> >
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1070/org/apache/accumulo/accumulo/1.9.0/accumulo-1.9.0-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: 8CC4F8A2B29C2B040F2B835D6F0CDAE700B6899D)
> > > >> >
> > > >> > Release notes (in progress) can be found at:
> > > >> > https://accumulo.apache.org/release/accumulo-1.9.0/
> > > >> >
> > > >> > 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.9.0 release of Apache Accumulo.
> > > >> >
> > > >> > This vote will remain open until at least Sun Apr 15 22:30:00 UTC
> > 2018
> > > >> > (Sun Apr 15 18:30:00 EDT 2018 / Sun Apr 15 15:30:00 PDT 2018).
> > > >> > Voting continues until the release manager sends an email closing
> > the
> > > >> vote.
> > > >> >
> > > >> > 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-1070/
> > > >> > # note the trailing slash is needed
> > > >>
> > > >
> > >
> >
>
Re: [RESULT][VOTE] Apache Accumulo 1.9.0-rc1
Posted by Christopher <ct...@apache.org>.
On Wed, Apr 18, 2018 at 3:21 PM Michael Wall <mj...@gmail.com> wrote:
> Congrats. Don't forget to update the release notes with the testing
> information to include versions. I didn't realize that 1.9 would work with
> Hadoop 3 but I see it in the parent pom as a profile. Also, did anything
> change as result of Sean and Mike's comments?
>
>
Regarding Hadoop 3 and testing,
Accumulo 1.9.0 will, in theory, work with Hadoop 3, because of the work
Josh did to check during development, and to modify the build... but using
it with Hadoop 3 may require building from source with the Hadoop 3
profile, or at least, require users to perform some packaging/integration
steps to set up the class path for their deployments with Hadoop 3. I don't
know if anybody has done any tests other than build tests with the profile
active. Also, some Hadoop 3 features may or may not be available, due to
lack of Accumulo ability to configure them (per-table HDFS erasure encoding
settings, for example, as an alternative to replication factor). In short,
user mileage may vary, but at least the option is there to try (because the
code compiles and the basic build tests pass).
Regarding Sean and Mike's comments:
In response to Sean and Mike's comments, I copied the tarballs to the SVN
dist/dev area, along with their SHA512 sums, but no votes were changed as a
result. I saw no indication in the discussion that anybody other than
myself examined those files to ensure they met expectations. I also
proposed a change in the thread to the release process as a result of Sean
and Mike's comments (specifically, to include the SHA512 for the tarballs,
directly in future vote threads), but have not heard a response back on
that proposal. I will likely proceed with a change to the build.sh script
to incorporate that proposal in a future pull request, unless somebody has
a better proposal before then.
> On Wed, Apr 18, 2018 at 2:59 PM Christopher <ct...@apache.org> wrote:
>
> > This vote passes with: 6*(+1) + 1*(-0) + 1*(-1)
> >
> > +1: edcoleman, mwalch, jmark99, ctubbsii, kturner, mmiller
> > -0: mdrob
> > -1: busbey
> >
> > Thanks for the votes all, I'll start working on the post-vote steps next.
> > It looks like folks are still making updates to the release notes.
> >
> > On Wed, Apr 18, 2018 at 2:47 PM Christopher <ct...@apache.org> wrote:
> >
> > > +1
> > >
> > > * Verified SVN staging area (dist/dev/accumulo/1.9.0-rc1) tarballs
> match
> > > Nexus staging area (artifacts and GPG sigs) and SHA512s there are
> > correct.
> > > * Ran mvn verify -DskipTests with both Hadoop 2 and Hadoop 3
> > > * Ran all ITs successfully with Hadoop 2
> > > * GPG signatures match release tarball artifacts (and other Maven
> > > artifacts)
> > > * Maven repo is consistent (all md5, sha1 sigs match their Maven
> > artifacts)
> > > * All jars have corresponding javadoc and source jars.
> > > * Contents of binary tarball lib directory match Maven jars
> > > * Source tarball matches git commit
> > > * Jar manifest indicates build from correct git commit
> > > * Jars are sealed
> > > * Using 1.9.0 jars, successfully built Apache Fluo (with ITs)|
> > > * Also attempted to build Hive... which works, but some Accumulo tests
> > > fail because of the use of "." in iterator names, which is broken, and
> > > explicitly checked for as of ACCUMULO-3389
> > > * Also attempted to build geowave, but that failed because geowave
> > appears
> > > to extensively make use of non-public API from Accumulo, so I gave up.
> > >
> > > I checked the LICENSE and NOTICE files also, and they look good, except
> > > for the fact that they still say 2017, instead of 2018. I can't
> believe I
> > > forgot to check this a second time, after this same thing happened for
> > > 1.7.4. In any case, I don't think it's worth holding up the release,
> > given
> > > that there do not seem to be any other serious issues with the
> artifacts.
> > >
> > >
> > > On Wed, Apr 18, 2018 at 11:07 AM Keith Turner <ke...@deenlo.com>
> wrote:
> > >
> > >> +1
> > >>
> > >> * Successfully built Fluo against RC
> > >> * Ran continuous ingest for 24hrs on 9 node cluster using RC.
> > >> Verified successfully. Table had 32.3 billion entries after test.
> > >>
> > >>
> > >>
> > >> On Thu, Apr 12, 2018 at 6:21 PM, Christopher <ct...@apache.org>
> > wrote:
> > >> > Accumulo Developers,
> > >> >
> > >> > Please consider the following candidate for Apache Accumulo 1.9.0.
> > >> >
> > >> > Git Commit:
> > >> > bca516000bdb54b1e5582f908e0a525634a120f7
> > >> > Branch:
> > >> > 1.9.0-rc1
> > >> >
> > >> > If this vote passes, a gpg-signed tag will be created using:
> > >> > git tag -f -m 'Apache Accumulo 1.9.0' -s rel/1.9.0 \
> > >> > bca516000bdb54b1e5582f908e0a525634a120f7
> > >> >
> > >> > Staging repo:
> > >> >
> > >>
> >
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1070
> > >> > Source (official release artifact):
> > >> >
> > >>
> >
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1070/org/apache/accumulo/accumulo/1.9.0/accumulo-1.9.0-src.tar.gz
> > >> > Binary:
> > >> >
> > >>
> >
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1070/org/apache/accumulo/accumulo/1.9.0/accumulo-1.9.0-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: 8CC4F8A2B29C2B040F2B835D6F0CDAE700B6899D)
> > >> >
> > >> > Release notes (in progress) can be found at:
> > >> > https://accumulo.apache.org/release/accumulo-1.9.0/
> > >> >
> > >> > 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.9.0 release of Apache Accumulo.
> > >> >
> > >> > This vote will remain open until at least Sun Apr 15 22:30:00 UTC
> 2018
> > >> > (Sun Apr 15 18:30:00 EDT 2018 / Sun Apr 15 15:30:00 PDT 2018).
> > >> > Voting continues until the release manager sends an email closing
> the
> > >> vote.
> > >> >
> > >> > 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-1070/
> > >> > # note the trailing slash is needed
> > >>
> > >
> >
>
Re: [RESULT][VOTE] Apache Accumulo 1.9.0-rc1
Posted by Michael Wall <mj...@gmail.com>.
Congrats. Don't forget to update the release notes with the testing
information to include versions. I didn't realize that 1.9 would work with
Hadoop 3 but I see it in the parent pom as a profile. Also, did anything
change as result of Sean and Mike's comments?
On Wed, Apr 18, 2018 at 2:59 PM Christopher <ct...@apache.org> wrote:
> This vote passes with: 6*(+1) + 1*(-0) + 1*(-1)
>
> +1: edcoleman, mwalch, jmark99, ctubbsii, kturner, mmiller
> -0: mdrob
> -1: busbey
>
> Thanks for the votes all, I'll start working on the post-vote steps next.
> It looks like folks are still making updates to the release notes.
>
> On Wed, Apr 18, 2018 at 2:47 PM Christopher <ct...@apache.org> wrote:
>
> > +1
> >
> > * Verified SVN staging area (dist/dev/accumulo/1.9.0-rc1) tarballs match
> > Nexus staging area (artifacts and GPG sigs) and SHA512s there are
> correct.
> > * Ran mvn verify -DskipTests with both Hadoop 2 and Hadoop 3
> > * Ran all ITs successfully with Hadoop 2
> > * GPG signatures match release tarball artifacts (and other Maven
> > artifacts)
> > * Maven repo is consistent (all md5, sha1 sigs match their Maven
> artifacts)
> > * All jars have corresponding javadoc and source jars.
> > * Contents of binary tarball lib directory match Maven jars
> > * Source tarball matches git commit
> > * Jar manifest indicates build from correct git commit
> > * Jars are sealed
> > * Using 1.9.0 jars, successfully built Apache Fluo (with ITs)|
> > * Also attempted to build Hive... which works, but some Accumulo tests
> > fail because of the use of "." in iterator names, which is broken, and
> > explicitly checked for as of ACCUMULO-3389
> > * Also attempted to build geowave, but that failed because geowave
> appears
> > to extensively make use of non-public API from Accumulo, so I gave up.
> >
> > I checked the LICENSE and NOTICE files also, and they look good, except
> > for the fact that they still say 2017, instead of 2018. I can't believe I
> > forgot to check this a second time, after this same thing happened for
> > 1.7.4. In any case, I don't think it's worth holding up the release,
> given
> > that there do not seem to be any other serious issues with the artifacts.
> >
> >
> > On Wed, Apr 18, 2018 at 11:07 AM Keith Turner <ke...@deenlo.com> wrote:
> >
> >> +1
> >>
> >> * Successfully built Fluo against RC
> >> * Ran continuous ingest for 24hrs on 9 node cluster using RC.
> >> Verified successfully. Table had 32.3 billion entries after test.
> >>
> >>
> >>
> >> On Thu, Apr 12, 2018 at 6:21 PM, Christopher <ct...@apache.org>
> wrote:
> >> > Accumulo Developers,
> >> >
> >> > Please consider the following candidate for Apache Accumulo 1.9.0.
> >> >
> >> > Git Commit:
> >> > bca516000bdb54b1e5582f908e0a525634a120f7
> >> > Branch:
> >> > 1.9.0-rc1
> >> >
> >> > If this vote passes, a gpg-signed tag will be created using:
> >> > git tag -f -m 'Apache Accumulo 1.9.0' -s rel/1.9.0 \
> >> > bca516000bdb54b1e5582f908e0a525634a120f7
> >> >
> >> > Staging repo:
> >> >
> >>
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1070
> >> > Source (official release artifact):
> >> >
> >>
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1070/org/apache/accumulo/accumulo/1.9.0/accumulo-1.9.0-src.tar.gz
> >> > Binary:
> >> >
> >>
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1070/org/apache/accumulo/accumulo/1.9.0/accumulo-1.9.0-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: 8CC4F8A2B29C2B040F2B835D6F0CDAE700B6899D)
> >> >
> >> > Release notes (in progress) can be found at:
> >> > https://accumulo.apache.org/release/accumulo-1.9.0/
> >> >
> >> > 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.9.0 release of Apache Accumulo.
> >> >
> >> > This vote will remain open until at least Sun Apr 15 22:30:00 UTC 2018
> >> > (Sun Apr 15 18:30:00 EDT 2018 / Sun Apr 15 15:30:00 PDT 2018).
> >> > Voting continues until the release manager sends an email closing the
> >> vote.
> >> >
> >> > 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-1070/
> >> > # note the trailing slash is needed
> >>
> >
>