[
https://issues.apache.org/jira/browse/HBASE-14175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16409635#comment-16409635
]
Sean Busbey commented on HBASE-14175:
-------------------------------------
For branch-1.2 I've been following the CHANGES guidance that I wrote up back
when 1.2.0 became stable. Essentially, the CHANGES file has 1.0.0 release
notes, then 1.1.0 release notes, then 1.2.*. This allows someone upgrading from
pre-1.0 to see all the relevant changes for whichever 1.2.z release they pick.
I do not know if RMs after me on branches-1 similarly tracked just the dot-0
for minors previous to them and then each maintenance release on their minor
line.
> 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)
