[
https://issues.apache.org/jira/browse/HBASE-22516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16854901#comment-16854901
]
Wellington Chevreuil commented on HBASE-22516:
----------------------------------------------
Right, so revisiting original check-list:
{quote}review LICENSE / NOTICE files{quote}
I believe we are good here, per the latest comments above.
{quote}Make sure rat says our files are fine wrt license headers (mvn
apache-rat:check){quote}
I believe we are fine also:
{noformat}
[INFO] --- apache-rat-plugin:0.12:check (default-cli) @ hbase-filesystem ---
[INFO] Enabled default license matchers.
[INFO] Will parse SCM ignores for exclusions...
[INFO] Parsing exclusions from
/Users/wellingtonchevreuil/Projects/hbase-filesystem-repo/hbase-filesystem/.gitignore
[INFO] Finished adding exclusions from SCM ignore files.
[INFO] 65 implicit excludes (use -debug for more details).
[INFO] No excludes explicitly specified.
[INFO] 3 resources included (use -debug for more details)
[INFO] Rat check: Summary over all files. Unapproved: 0, unknown: 0, generated:
0, approved: 1 licenses.
[INFO]
[INFO] ---------------< org.apache.hbase.filesystem:hbase-oss >----------------
[INFO] Building Apache HBase / Object-Store Semantics Module 1.0.0-alpha [2/2]
[INFO] --------------------------------[ jar ]---------------------------------
[INFO]
[INFO] --- apache-rat-plugin:0.12:check (default-cli) @ hbase-oss ---
[INFO] Enabled default license matchers.
[INFO] Will parse SCM ignores for exclusions...
[INFO] Finished adding exclusions from SCM ignore files.
[INFO] 61 implicit excludes (use -debug for more details).
[INFO] No excludes explicitly specified.
[INFO] 39 resources included (use -debug for more details)
[INFO] Rat check: Summary over all files. Unapproved: 0, unknown: 0, generated:
0, approved: 37 licenses.
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] Apache HBase FileSystem-related Modules 1.0.0-alpha SUCCESS [ 0.870 s]
[INFO] Apache HBase / Object-Store Semantics Module 1.0.0-alpha SUCCESS [
0.090 s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
{noformat}
{quote}Check git vs jira for a correct list of issues included in the
release{quote}
Should we have a specific release file enumerating these? Here's the list of
jiras committed to master: HBASE-22515, HBASE-22415, HBASE-22427, HBASE-22393,
HBASE-22493, HBASE-22437, HBASE-22416, HBASE-22386, HBASE-22149.
{quote}use Apache Yetus Release Doc Maker to generate release notes / changes
and check into repo{quote}
TODO
{quote}update versions to be non-SNAPSHOT{quote}
[PR|https://github.com/apache/hbase-filesystem/pull/3] with changes available.
{quote}make sure we can still build jars{quote}
After changing the versions? If so, yeah, current versions values from PR above
does allow for building jars.
{quote}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){quote}
Waiting version value change.
{quote}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){quote}
Waiting version value change.
{quote}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.{quote}
Pending previous required task.
{quote}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 ref guide section for the main
project){quote}
Pending previous required task.
{quote}call VOTE for release candidate. Include the staged artifacts, staged
maven repository, any critical issues that need summary{quote}
Pending previous required task.
{quote}iterate on RCs if needed due to VOTE feedback{quote}
Pending previous required task.
{quote}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{quote}
Pending previous required task.
> 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)
