[
https://issues.apache.org/jira/browse/HBASE-14175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16408729#comment-16408729
]
stack commented on HBASE-14175:
-------------------------------
Updated my yetus and then did this: {{yetus.git stack$
./release-doc-maker/releasedocmaker.py -p HBASE --version 2.0.0
--dirversions}} I now have lovely .md release notes and changes.
How should I integrate them? Currently we do not ship a release notes and our
Changes is a .txt file currently last updated for 0.92 in branch-2. Over in
branch-1, I see that 1.2.7 has a nice text changes that goes back to 1.0.0.
{{yetus.git stack$ ./release-doc-maker/releasedocmaker.py -p HBASE --range
--version 1.0.0 --version 2.0.0 --dirversions}}
will dump out files per version. I can collapse the whole lot and edit to make
a new CHANGES.txt file for branch-2. Could also check in these release notes
and the markdown (checking in release notes might encourage devs to do a better
job writing them).
> 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
> 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)
