Agree with Duo. I think changes in that minor release line are the most meaningful to users without being too much of a burden for devs.

On 6/10/19 11:06 AM, 张铎(Duo Zhang) wrote:
I prefer we include all the diffs in this minor release line in the
CHANGES.md. For example, 2.1.1 will also contains the contents for 2.1.0.
But I do not think it is necessary to contain all the changes from the
beginning, it will be too large...

Stack <[email protected]> 于2019年6月10日周一 下午10:54写道:

I was under the impression that our CHANGES.md was a list of all changes
since the beginning of time but branch-2.2 only has 2.2.0 changes and
Guanghao points out that hbase-2.1 releases have CHANGES only since 2.1.0
(I'm RM on branch-2.1).

I see Sean say in another thread says

   "Historically that has meant "all the maintenance releases in this minor
release".

(Andrew thinks we should not bundle CHANGES.md/RELEASENOTES.md but just
point elsewhere and/or to JIRA).

What do folks think? I think these docs should have all changes in them;
i.e. that branch-2.1 is doing it wrong?

Thanks,
S


Reply via email to