stack created HBASE-22573:
-----------------------------
Summary: RELEASENOTES/CHANGES have all patch changes in a minor
release and then a pointer to older changes
Key: HBASE-22573
URL: https://issues.apache.org/jira/browse/HBASE-22573
Project: HBase
Issue Type: Bug
Reporter: stack
Implement common agreement reached up on the dev list about how to do
CHANGES.md and RELEASENOTES.md going forward (See
http://mail-archives.apache.org/mod_mbox/hbase-dev/201906.mbox/%3CCADcMMgFh54G=a8h1u3ufRAW3oJ3HPH=jfzzm7at4vkhyihn...@mail.gmail.com%3E)
for branches 2.1/2.2 and beyond.
In branch-1 releases and in branch-2.0, the CHANGES.md/RELEASENOTES.md listed
all JIRAs that made up a release (HBASE-14025 has some definition of the
practice for branch-1.2). In branch-2.1, we (I) inadvertently listed changes
in the minor branch only. branch-2.2 picked up this practice. Going forward we
agree that we should continue the branch-2.1 behavior but with the caveat that
we add a pointer to older changes to the tail of the CHANGES.md and RL.md files.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
