Stig Rohde Døssing created STORM-2665:
-----------------------------------------
Summary: Replace CHANGELOG with an automatic solution
Key: STORM-2665
URL: https://issues.apache.org/jira/browse/STORM-2665
Project: Apache Storm
Issue Type: Improvement
Reporter: Stig Rohde Døssing
Priority: Minor
Background here
http://mail-archives.apache.org/mod_mbox/storm-dev/201707.mbox/%3CCAG09ER0CUcoSCgEpJyK7hgbfKczO1HTjRVoUogaOgzozA5Ckdg%40mail.gmail.com%3E
The proposed replacements for CHANGELOG.md in the thread have been (apologies
if I missed any):
* Following certain commit log standards, and deriving the change log from the
commits since last release
* Ensuring that committers update JIRA fix versions when issues are resolved,
and pulling the change log from there by a script or manually. A place to start
for this is looking at borrowing Kafka's script for generating release notes at
https://github.com/apache/kafka/blob/trunk/release_notes.py
* Ensuring that committers update JIRA fix versions when issues are resolved,
and linking to the relevant JIRA query from the release notes
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
