[
https://issues.apache.org/jira/browse/HBASE-22516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16854673#comment-16854673
]
Wellington Chevreuil commented on HBASE-22516:
----------------------------------------------
Hi [~busbey], thanks for enumerating the above bullets. Few doubts on some of
those:
{quote}review LICENSE / NOTICE files{quote}
Comparing current NOTICE file with the one from HBase main project, noticed
that we mention hbase depends on hadoop, guava and bootstrap. We are importing
and shading some third party dependencies here on hboss (including guava), as
well as completely depending on hadoop file system contracts. Should all these
be pointed on NOTICE file? For LICENSE file, hbase project mentions all
additional dependencies under different licenses (jquery, protobuf, adoctor).
Is this only needed for direct dependencies, say for instance hboss relies on
protobuf under the hood, should we include such section on LICENSE as well?
{quote}update versions to be non-SNAPSHOT{quote}
Just to be sure, this is just to change version on related pom file, right?
Should then submit the change as patch on this jira?
Additional, question: Should we also include "update [170. Apache HBase
Repositories|https://hbase.apache.org/book.html#repos] section from ref guide"
to add hbase-filesystem repository as one of the release steps, or would that
something to be changed once the release is effective?
> release hbase-filesystem version 1.0.0-alpha1
> ---------------------------------------------
>
> Key: HBASE-22516
> URL: https://issues.apache.org/jira/browse/HBASE-22516
> Project: HBase
> Issue Type: Task
> Components: community, Filesystem Integration
> Affects Versions: hbase-filesystem-1.0.0-alpha1
> Reporter: Sean Busbey
> Assignee: Wellington Chevreuil
> Priority: Major
> Fix For: hbase-filesystem-1.0.0-alpha1
>
>
> for this first alpha release we haven't evaluated deployment options yet, so
> let's just rely on maven for convenience binaries.
> Rough outline of process:
> # review LICENSE / NOTICE files
> # Make sure rat says our files are fine wrt license headers ({{mvn
> apache-rat:check}})
> # Check git vs jira for a correct list of issues included in the release
> # use Apache Yetus Release Doc Maker to generate release notes / changes and
> check into repo
> # update versions to be non-SNAPSHOT
> # make sure we can still build jars
> # tag RC ({{git tag -s 1.0.0-alpha1-RC0 -m "HBASE-XXXX Tagging the
> 1.0.0-alpha1 first Releae Candidate" && git push origin 1.0.0-alpha1-RC0}})
> # use the git archive command to create a source artifact ({{git archive
> --format=tar.gz
> --output="/tmp/hbase-filesystem-1.0.0-alpha1-RC0/hbase-filesystem-1.0.0-alpha1-src.tar.gz"
> --prefix="hbase-filesystem-1.0.0-alpha1/" 1.0.0-alpha1-RC0}})
> # stage the RC artifacts somewhere accessible by https. Should include
> release notes, changes, and source artifact. each of those should have a gpg
> signature and a sha512 checksum file.
> # stage maven repository (tl;dr: {{mvn deploy -DskipTests -Papache-release}}
> and then https://repository.apache.org. See the longer explanation under the
> steps "Deploy to the Maven Repository" and "Make the Release Candidate
> available" in the [Making a Release
> Candidate|http://hbase.apache.org/book.html#maven.release] ref guide section
> for the main project)
> # call VOTE for release candidate. Include the staged artifacts, staged maven
> repository, any critical issues that need summary
> # iterate on RCs if needed due to VOTE feedback
> # When VOTE passes, tag {{rel/1.0.0-alpha1}}, release maven repository,
> publish artifacts on dist.apache.org, send ANNOUNCE email, and prepare repo
> for further development
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
