Sure thing. Filed HBASE-15738
On Fri, Apr 29, 2016 at 1:53 PM, Andrew Purtell <[email protected]> wrote: > Thanks for voting +1 on the release Sean. > >> I don't want to hold up this vote, but I plan to start voting -1 on > future RCs that don't include md5 files. > > Our release documentation (https://hbase.apache.org/book.html#releasing) > says we should generate sums like so: > > for i in *.tar.gz; do echo $i; gpg --print-mds $i > $i.mds ; done > > > The make_rc.sh script also encodes the same. Let's fix. > >> this commit is pointed to by tag 0.98.19RC0. It's not included in the > line of commits that reach the current head for the 0.98 branch, but the > same content appears on that branch. > > I forgot to push the 0.98 branch for 24 hours after setting the tag and Ted > made a commit in the meantime. Apologies. > > > > > On Fri, Apr 29, 2016 at 11:42 AM, Sean Busbey <[email protected]> wrote: > >> +1 >> >> * checked signatures / sums[1] >> * checked LICENSE/NOTICE and git log for updates >> * spot checked file header compliance using apache-rat plugin on clean >> source unpack >> * build from source[2] >> * source matches commit 1e527e73bc539a04ba0fa4ed3c0a82c7e9dd7d15[3] >> >> >> [1]: ASF policy requires that each file hosted in the project dist >> space have a file with _just_ the MD5 sum in a file named after the >> original with ".md5" as a suffix. (Having an additional file with all >> the checksums is a good practice, IMO.) I brought this up in our last >> round of RCs as well. I don't want to hold up this vote, but I plan to >> start voting -1 on future RCs that don't include md5 files. >> >> relevant policy: >> http://www.apache.org/dev/release-distribution.html#sigs-and-sums >> >> [2]: I had a couple of test failures in mvn verify, but they were of >> the "waiting for hbase to start" variety or timeouts. For the curious, >> it currently >> takes ~8 hours for "mvn --fail-never clean package verify" to finish >> on my laptop. >> >> [3]: this commit is pointed to by tag 0.98.19RC0. It's not included in the >> line >> of commits that reach the current head for the 0.98 branch, but the same >> content appears on that branch. >> >> On Fri, Apr 22, 2016 at 9:51 PM, Andrew Purtell <[email protected]> >> wrote: >> > The 1st HBase 0.98.19 release candidate (RC0) is available for download >> at >> > https://dist.apache.org/repos/dist/dev/hbase/0.98.19RC0/ and Maven >> > artifacts are also available in the temporary repository >> > https://repository.apache.org/content/repositories/orgapachehbase-1135 . >> > >> > The detailed source and binary compatibility report for this release with >> > respect to the previous is available for your review at >> > >> https://dist.apache.org/repos/dist/dev/hbase/0.98.19RC0/0.98.18_0.98.19RC0_compat_report.html >> > . There are no reported problems or warnings. >> > >> > The 43 issues resolved in this release can be found at >> > https://s.apache.org/9AiE >> > >> > I have made the following preliminary assessments of this candidate: >> > - Build with source artifact with RAT and enforcers enabled (-Prelease) >> > completes successfully >> > - Unit test suite passes 20 of 20 iterations (7u79) >> > - Loaded 1M rows with LTT (10 readers, 10 writers, >> > 10 updaters @ >> > 20%), nothing unusual logged, >> > all keys verified, >> > reported latencies in the ballpark >> > - Built and ran unit tests with head of Apache Phoenix 4.x-HBase-0.98 >> > branch, looks good (7u79) >> > >> > Signed with my code signing key 4B6D7DF3. >> > >> > Please try out the candidate and vote +1/0/-1. This vote will be open for >> > at least 72 hours. Unless objection I will try to close it Friday April >> 29, >> > 2016 if we have sufficient votes. Three +1 votes from PMC will be >> required >> > to release. >> > >> > -- >> > Best regards, >> > >> > - Andy >> > >> > Problems worthy of attack prove their worth by hitting back. - Piet Hein >> > (via Tom White) >> > > > > -- > Best regards, > > - Andy > > Problems worthy of attack prove their worth by hitting back. - Piet Hein > (via Tom White)
