aurora-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bill Farner (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (AURORA-300) changelog generation should document potentially breaking API changes
Date Sun, 24 Apr 2016 15:43:12 GMT

     [ https://issues.apache.org/jira/browse/AURORA-300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Bill Farner resolved AURORA-300.
--------------------------------
    Resolution: Fixed

Agreed, closing.

> 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)

Mime
View raw message