On Mon, Jun 10, 2019 at 9:08 AM Andrew Purtell <[email protected]> wrote:
> ...How big would a Yetus generated release notes file be if it includes > changes all the way back to HBASE-1? > RELEASENOTES.md in branch-2.0 is almost 500k. CHANGES.md is coming up on a megabyte. HBase 2.0 branch has the yetus generated stuff for each minor release since 2.0.0. The tail of the CHANGES.md has 1.0.0 release notes and older (02/20/2015); i.e. 1.0.0 changes + all that made 2.0.0. RELEASENOTES.md is new to 2.0.0. S > > > On Jun 10, 2019, at 8:16 AM, Stack <[email protected]> wrote: > > > >> On Mon, Jun 10, 2019 at 8:05 AM Sean Busbey <[email protected]> wrote: > >> > >> Back for the 1.2 release line I tried to include enough information > >> that someone looking at the given 1.2 release coming from the prior > >> major version would have everything. > >> > >> That meant: > >> > >> * 1.0.0 release notes > >> * 1.1.0 release notes > >> * 1.2.z (for all z 0-12) release notes > >> > >> https://github.com/apache/hbase/blob/branch-1.2/CHANGES.txt > > > > > > > > Yeah, this is how it has been in all releases until 2.1 where I seem to > > have broken the practice (I just looked at the 1.4.10 RC and notice that > > Andrew follows the above practice. 2.0.x has all CHANGES). > > > > > > > >> I do not know if this was actually useful. This seems like a > >> conversation better had on user@hbase, tbh. > >> > >> > > I can ask over there too. > > > > > > S > > > > > > > > > > > >> (folks interested in background material, the last time we talked > >> about this was in HBASE-14025 in 2015 and 2016) > >> > > > > > > > >>> On Mon, Jun 10, 2019 at 9:54 AM Stack <[email protected]> wrote: > >>> > >>> 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 > >> >
