stack commented on HBASE-18828:

Ok. Pushed .003 to branch-2.0. I then pushed an addendum that adds a comment to 
head of the two new files that talks up how they were generated pointing back 
to HBASE-14175 and to here:

+CHANGES.md and RELEASENOTES.md were generated using yetus releasedocmaker.
+First make sure what is in JIRA agrees with what is in git and vice-versa
+(See HBASE-14175 for original exposition on how to do this followed by
+the travails of various release managers. See also HBASE-18828 for a
+deriviative makes the move to yetus releasedocmaker).
+Then make sure that anything in current release as noted in JIRA has
+not made it out in earlier major/minor (see HBASE-14175 for how to
+reconcile which).
+Obtain a yetus release (see HBASE-18828 for some help). To run
+releasedocmaker, do as follows (below example is for hbase-2.0.0):
+ $ ./release-doc-maker/releasedocmaker.py -p HBASE --fileversions \
+    -v 2.0.0 -l --sortorder=newer --skip-credits
+Rename the output as CHANGES.md and RELEASENOTES.md. Edit both to put
+document title above the apache license so markdown readers work. You
+may have to bulk import old-style CHANGES.txt on to the end in a code
+comment to preserve continuity of the CHANGELOG.

So, the CHANGES are current as of now. They will rot before I make the RC but 
it will just be a case of re-running the tool and some hackery... small 
potatoes. Let resolve this then as done and just add a note on releasing 2.0.0 
to make sure I do the regeneration. The hard work is done in here (the 
resolving git and JIRA records).

> [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
>         Attachments: HBASE-18828.branch-2.0.001.patch, 
> HBASE-18828.branch-2.0.002.patch, HBASE-18828.branch-2.0.003.patch, 
> changelog.md, hbase_branches.svg, releasenotes.md
> See [~busbey] writeup on generating CHANGES.txt here HBASE-14025 (fold it 
> into refguide while at it..)

This message was sent by Atlassian JIRA

Reply via email to