[
https://issues.apache.org/jira/browse/AURORA-300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Sweeney updated AURORA-300:
---------------------------------
Description:
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
was:
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
> 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
--
This message was sent by Atlassian JIRA
(v6.2#6252)
