You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@samza.apache.org by "Prateek Maheshwari (JIRA)" <ji...@apache.org> on 2017/05/03 20:23:04 UTC

[jira] [Updated] (SAMZA-1177) Improve upgrade documentation for open source releases

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

Prateek Maheshwari updated SAMZA-1177:
--------------------------------------
    Fix Version/s:     (was: 0.13.0)
                   0.14.0

> Improve upgrade documentation for open source releases
> ------------------------------------------------------
>
>                 Key: SAMZA-1177
>                 URL: https://issues.apache.org/jira/browse/SAMZA-1177
>             Project: Samza
>          Issue Type: Bug
>            Reporter: Jagadish
>             Fix For: 0.14.0
>
>
> Currently, the only form of documentation for a release we have is our release blog-posts on the Apache blog. However, this has several problems:
> - No single trail of audits for various releases
> - While we allow upgrades to be seamless from previous releases to the next ones, we don't document what breaks when users skip versions (when upgrading).
> The Kafka release page at https://kafka.apache.org/documentation/#upgrade is a good reference to emulate.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)