RAT check fails for me, below error I see in the log file,

4 Unknown Licenses

*****************************************************

Files with unapproved licenses:

  hbase-spark/target/test-classes.-284428056.timestamp
  hbase-spark/target/classes.786562742.timestamp
  hbase-spark/target/maven-archiver/pom.properties
  hbase-prefix-tree/target/maven-archiver/pom.properties

*****************************************************

CHANGES.txt file doesn't look correct.



Downloaded the binary and checked the following,

- Checked LICENSE and NOTICE files, looks ok

Verified the following in a non-kerberos setup,
- On a one node setup did upgrade from 1.3.2-SNAPSHOT version to
2.0.0-beta-1
- Performed get and scan operation on data which were loaded in
1.3.2-SNAPSHOT version
- Exercised basic shell commands
- Ran LTT with 1M row, checked read and write operations
- Poked around webUI
- Started Rest server and executed few commands
- Checked logs
- Browsed book

Regards,
Ashish

On Sat, Jan 13, 2018 at 10:18 AM, Stack <st...@duboce.net> wrote:

> The fourth release candidate for HBase 2.0.0-beta-1 is up at:
>
>   https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0-beta-1-RC3/
>
> Maven artifacts are available from a staging directory here:
>
>   https://repository.apache.org/content/repositories/orgapachehbase-1193
>
> All was signed with my key at 8ACC93D2 [1].
>
> I tagged the RC as 2.0.0-beta-1-RC1.7 at hash 026f535a7747b89003252ded9
> 585e827686aa79f
>
> This RC has some nice bug fixes over RC0-2 including fixing MOST of the
> failing and flakey tests (We are still working through them).
>
> hbase-2.0.0-beta-1 is our first beta release. It includes all that was in
> previous alphas (new assignment manager, offheap read/write path, in-memory
> compactions, etc.). The APIs and feature-set are sealed.
>
> hbase-2.0.0-beta-1 is a not-for-production preview of hbase-2.0.0. It is
> meant for devs and downstreamers to test drive and flag us if we messed up
> on anything ahead of our rolling GAs. We are particular interested in
> hearing from Coprocessor developers.
>
> The list of features addressed in 2.0.0 so far can be found here [3]. There
> are thousands. The list of ~2k+ fixes in 2.0.0 exclusively can be found
> here [4] (My JIRA JQL foo is a bit dodgy -- forgive me if mistakes).
>
> I've updated our overview doc. on the state of 2.0.0 [6]. We'll do one more
> beta before we put up our first 2.0.0 Release Candidate by the end of
> January, 2.0.0-beta-2. Its focus will be making it so users can do a
> rolling upgrade on to hbase-2.x from hbase-1.x (and any bug fixes found
> running beta-1). Here is the list of what we have targeted so far for
> beta-2 [5]. Check it out.
>
> One known issue is that the User API has not been properly filtered so it
> shows more than just InterfaceAudience Public content (HBASE-19663, to be
> fixed by beta-2).
>
> Please take this beta for a spin. Please vote on whether it ok to put out
> this RC as our first beta (Note CHANGES has not yet been updated). Let the
> VOTE be open for 72 hours (Lets say Tuesday morning!)
>
> Thanks,
> Your 2.0.0 Release Manager
>
> 1. http://pgp.mit.edu/pks/lookup?op=get&search=0x9816C7FC8ACC93D2
> 3. https://goo.gl/scYjJr
> 4. https://goo.gl/dFFT8b
> 5. https://issues.apache.org/jira/projects/HBASE/versions/12340862
> 6. https://docs.google.com/document/d/1WCsVlnHjJeKUcl7wHwqb4
> z9iEu_ktczrlKHK8N4SZzs/
>

Reply via email to