You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by GitBox <gi...@apache.org> on 2019/05/02 13:07:13 UTC

[GitHub] [hbase-filesystem] busbey commented on issue #1: HBASE-22149. HBOSS: A FileSystem implementation to provide HBase's re…

busbey commented on issue #1: HBASE-22149. HBOSS: A FileSystem implementation to provide HBase's re…
URL: https://github.com/apache/hbase-filesystem/pull/1#issuecomment-488665380
 
 
   I've finished looking at e.g. project structure and things that would block a alpha1 source release.
   
   I'd still like to see follow-on jiras to make sure we track:
   
   * Profiles for Hadoop 2 and Hadoop 3
   * coming up with what convenience binaries look like (including handling LICENSE/NOTICE)
   * review of InterfaceAudience labels prior to release
   * docs indicating what Hadoop 2/3 versions to expect to work
   * docs indicating what HBase versions we're expecting to work
   * Setting up nightly / precommit tests
   * At least nightly tests checking building with one maintenance release from each minor listed in the Hadoop 2/3 versions that work
   * At least nightly tests that check building with one maintenance release from each minor listed HBase versions
   * Ideally at least one nightly test that tries to run an instance against a specific HBase/Hadoop combo with whatever lock manager we *think* will be the most commonly used.
   * making an alpha release (even if it's just source)
   
   what are other folks thinking? is this at a place where it's implemented enough to serve as a starting point?

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services