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] [Commented] (AURORA-300) changelog generation should document potentially breaking API changes
Date Wed, 29 Apr 2015 15:30:08 GMT

    [ https://issues.apache.org/jira/browse/AURORA-300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14519558#comment-14519558
] 

Bill Farner commented on AURORA-300:
------------------------------------

[~kevints] how would you feel about integrating this into our development process instead?
 i.e. include an edit to the changelog when a relevant change is made.  This would make it
much more natural to roll things up at release time, and would allow us to include prose incrementally.

> 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