[
https://issues.apache.org/jira/browse/HBASE-18828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16408783#comment-16408783
]
stack commented on HBASE-18828:
-------------------------------
Just messed around with HBASE-14175 "Adopt releasedocmaker for better generated
release notes". Also took a look again at notes in HBASE-14025. Let me play
more w/ releasedocmaker. Need to minimally follow the suggested cleanup in
HBASE-14025.
Meantime, toward the goal of generating clean releasenotes/changes, I just did
a first pass over JIRA where I did an mass-edit of fixedVersions in-line with
the thinking expressed in HBASE-14025.
* High-level I added 2.0.0 to issues that had only 2.0.0-beta-1 or
2.0.0-alpha-2, etc., as fixVersion so now they have 2.0.0 AND 2.0.0-beta-2.
This way I can pull 2.0.0 from JIRA and it will include fixes in all alphas and
betas too.
* No JIRAs had 2.0.0-alpha-1 as fixVersion. Issues had 2.0.0 as their fix
version at time of the 2.0.0-alpha-1 release.
* Any 2.0.0 issue that also had 3.0.0 as fixVersion had the 3.0.0 removed (in
the HBASE-14025 spirit.
I was able to successfully generate 2.0.0 'release notes' from JIRA though
there are thousands.
TODO: Get HBASE-14025 notions into refguide.
TODO: See if place for releasedocmaker.
> [2.0] Generate CHANGES.txt
> --------------------------
>
> Key: HBASE-18828
> URL: https://issues.apache.org/jira/browse/HBASE-18828
> Project: HBase
> Issue Type: Sub-task
> Reporter: stack
> Assignee: stack
> Priority: Blocker
> Fix For: 2.0.0
>
>
> See [~busbey] writeup on generating CHANGES.txt here HBASE-14025 (fold it
> into refguide while at it..)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
