[
https://issues.apache.org/jira/browse/AURORA-300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14519882#comment-14519882
]
Kevin Sweeney commented on AURORA-300:
--------------------------------------
[~wfarner] I like that idea. Would still be nice to have tooling support to
warn against non-updated changelog for the changes that can be programmatically
detected (e.g. API changes). I like Guava's release notes as a model:
https://code.google.com/p/guava-libraries/wiki/Release18
> changelog generation should document potentially breaking API changes
> ---------------------------------------------------------------------
>
> Key: AURORA-300
> URL: https://issues.apache.org/jira/browse/AURORA-300
> Project: Aurora
> Issue Type: Story
> Components: Client, Executor, Scheduler
> Reporter: Kevin Sweeney
> Priority: Minor
>
> Minimally it should capture
> * Command-line flag changes for Scheduler, Executor, Thermos CLI, Client CLI
> * Public Thrift API changes (TODO: Specify Thrift API)
> * Hooks API changes
> Additionally it might capture language-level changes like
> Java API changes (+/- anything with public)
> * Use something like https://github.com/trnl/clirr-gradle-plugin
> Python API changes
> Stat names added/removed
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
