Repository: hbase
Updated Branches:
  refs/heads/branch-2.0 d7547c615 -> d4aee75f3


HBASE-18828 [2.0] Generate CHANGES.txt; ADDENDUM that adds comment to head of 
CHANGES.md and RELEASENOTES.md on how they were made


Project: http://git-wip-us.apache.org/repos/asf/hbase/repo
Commit: http://git-wip-us.apache.org/repos/asf/hbase/commit/d4aee75f
Tree: http://git-wip-us.apache.org/repos/asf/hbase/tree/d4aee75f
Diff: http://git-wip-us.apache.org/repos/asf/hbase/diff/d4aee75f

Branch: refs/heads/branch-2.0
Commit: d4aee75f3b6d4c7f896aed7a20cc75ac012a5126
Parents: d7547c6
Author: Michael Stack <st...@apache.org>
Authored: Sat Apr 7 09:54:27 2018 -0700
Committer: Michael Stack <st...@apache.org>
Committed: Sat Apr 7 09:54:27 2018 -0700

----------------------------------------------------------------------
 CHANGES.md      | 24 ++++++++++++++++++++++++
 RELEASENOTES.md | 25 +++++++++++++++++++++++++
 2 files changed, 49 insertions(+)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/hbase/blob/d4aee75f/CHANGES.md
----------------------------------------------------------------------
diff --git a/CHANGES.md b/CHANGES.md
index 493ac79..62af426 100644
--- a/CHANGES.md
+++ b/CHANGES.md
@@ -15,6 +15,30 @@
  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
  See the License for the specific language governing permissions and
  limitations under the License.
+
+
+
+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.
 -->
 
 ## Release 2.0.0 - Unreleased (as of 2018-04-06)

http://git-wip-us.apache.org/repos/asf/hbase/blob/d4aee75f/RELEASENOTES.md
----------------------------------------------------------------------
diff --git a/RELEASENOTES.md b/RELEASENOTES.md
index 7776c08..6b11c63 100644
--- a/RELEASENOTES.md
+++ b/RELEASENOTES.md
@@ -16,6 +16,31 @@
 # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
 # See the License for the specific language governing permissions and
 # limitations under the License.
+
+
+
+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.
+
 -->
 
 These release notes cover new developer and user-facing incompatibilities, 
important issues, features, and major improvements.

Reply via email to