[
https://issues.apache.org/jira/browse/HBASE-14175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16409642#comment-16409642
]
Sean Busbey commented on HBASE-14175:
-------------------------------------
Personally, I'd like to see the output (or an edited version) from
release-doc-maker as a polished view of what's in *just* a specific release,
and see that in artifacts and the website (as we each previously mentioned). I
agree that getting them visible would help immensely to encourage folks to take
the time to write them proactively, rather than waiting for an RM to ask them
to add it after the fact.
At least for now, I'd also like to see us continue to maintain the CHANGES.txt
file in the source artifact as well (ideally using the same "minor dot-0s in
this major and then maintenance versions within this minor" approach that has
been done in branch-1.2).
> 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)
