Thanks for the vote Josh. > Copyright in NOTICE needs updating for 2018
HBASE-20088 > we need to update the checksum naming convention for SHA HBASE-20089 On Mon, Feb 26, 2018 at 9:24 AM, Josh Elser <els...@apache.org> wrote: > +1 (binding) > > * src release contents looks OK > * sigs/xsums OK > * apache-rat:check OK > * Can build src release > * LICENSE looks OK > * Copyright in NOTICE needs updating for 2018 > > Only thing I noticed is that we need to update the checksum naming > convention for SHA*. Per [1], .sha filenames should only contain SHA1, and > .sha512 file names should be used for SHA512 xsum. I believe this means we > just need to modify make_rc.sh to put the xsum into .sha512 instead of > .sha. We do not need to distribute SHA1 xsums and, afaik, there is little > cryptographic value to this. > > [1] http://www.apache.org/dev/release-distribution.html#sigs-and-sums > > On 2/22/18 6:55 PM, Andrew Purtell wrote: > >> The second HBase 1.4.2 release candidate (RC1) is available for download >> at >> https://dist.apache.org/repos/dist/dev/hbase/hbase-1.4.2RC1/ and Maven >> artifacts are available in the temporary repository >> https://repository.apache.org/content/repositories/orgapachehbase-1196/ . >> >> The git tag corresponding to the candidate is '1.4.2RC1' (b4ec89059c). >> Note >> this is different from branch-1.4 by one commit because we had an >> intervening commit between tag and push (08b9939974, HBASE-20016) while I >> was running tests. The only difference is the CHANGES.txt update for >> 1.4.2RC1 is placed ahead of the commit for HBASE-20016, but does not >> mention it, which is fine, because 1.4.2RC1 does not contain HBASE-20016. >> >> A detailed source and binary compatibility report for this release is >> available for your review at >> https://dist.apache.org/repos/dist/dev/hbase/hbase-1.4.2RC1/ >> compat-check-report.html >> . >> >> A list of the 22 issues resolved in this release can be found at >> https://s.apache.org/aGcb . >> >> 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 Thursday February 28, 2018 if we have sufficient votes. >> >> Prior to making this announcement I made the following preflight checks: >> >> - RAT check passes (7u80) >> - Unit test suite passes (8u131) >> - LTT load 1M rows with 100% verification and 20% updates (8u131) >> - PE sequentialWrite, sequentialRead, randomWrite, randomRead, >> scanRange100 (8u131) >> - ITBLL Loop 1 100M rows (8u131) >> >> >> >>
