[ https://issues.apache.org/jira/browse/HBASE-14025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14614022#comment-14614022 ]
stack commented on HBASE-14025: ------------------------------- What you thinking [~busbey] If it helps: In past, you could not export more than 100 issues at a time from JIRA so making the CHANGES.txt content when > 100 issues was painful. Often, just punted and pointed at the release notes report in JIRA. Even when an export, hackery coming up w/ the form that always screamed 'script it' but was always too lazy to do it; instead just bungled through regex'ing in editor. > Update CHANGES.txt for 1.2 > -------------------------- > > Key: HBASE-14025 > URL: https://issues.apache.org/jira/browse/HBASE-14025 > Project: HBase > Issue Type: Sub-task > Components: documentation > Affects Versions: 1.2.0 > Reporter: Sean Busbey > Assignee: Sean Busbey > Fix For: 1.2.0 > > > Since it's more effort than I expected, making a ticket to track actually > updating CHANGES.txt so that new RMs have an idea what to expect. > Maybe will make doc changes if there's enough here. -- This message was sent by Atlassian JIRA (v6.3.4#6332)