You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2018/04/06 17:09:00 UTC

[jira] [Resolved] (HBASE-14175) Adopt releasedocmaker for better generated release notes

     [ https://issues.apache.org/jira/browse/HBASE-14175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

stack resolved HBASE-14175.
---------------------------
      Resolution: Fixed
        Assignee: stack
    Release Note: 
We will use yetus releasedocmaker to make our changes doc from here on out. A CHANGELOG.md will replace our current CHANGES.txt. Adjacent, we'll keep up a RELEASENOTES.md doc courtesy of releasedocmaker.

Over in HBASE-18828 is where we are working through steps for the RM integrating this new tooling.

Resolving. Will use releasedocmaker from 2.0.0 onward. Thanks for inputs.

> Adopt releasedocmaker for better generated release notes
> --------------------------------------------------------
>
>                 Key: HBASE-14175
>                 URL: https://issues.apache.org/jira/browse/HBASE-14175
>             Project: HBase
>          Issue Type: Task
>            Reporter: Andrew Purtell
>            Assignee: stack
>            Priority: Critical
>             Fix For: 2.0.0
>
>
> We should consider adopting Hadoop's releasedocmaker for better release notes. This would pull out text from the JIRA 'release notes' field with clean presentation and is vastly superior to our current notes, which are simply JIRA's list of issues by fix version. Could hook it into the site build. A convenient part of Yetus to get up and running with. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)