Andrew Kyle Purtell created HBASE-25359:
-------------------------------------------
Summary: create-release scripts releasedocmaker step should be
optional
Key: HBASE-25359
URL: https://issues.apache.org/jira/browse/HBASE-25359
Project: HBase
Issue Type: Improvement
Reporter: Andrew Kyle Purtell
The create-release scripts assume, when invoking releasedocmaker and performing
surgery on CHANGES.md and RELEASENOTES.md during the 'tag' stage, that the
current RC step is RC0. The entirety of the generated CHANGES.md and
RELEASENOTES.md files are stitched in at the head, just below the ASF notice.
If we are at a RC step that is not zero, wouldn't this duplicate all CHANGES.md
and RELEASENOTES.md content for the release? There would be all the content
added for RC0, then the same content (with delta) added for RC1, and so on.
For this reason the releasedocmaker invocation should itself be optional.
For RC steps > 0, assume the RM has updated CHANGES.md and RELEASENOTES.md to
reflect the delta.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
