[
https://issues.apache.org/jira/browse/KAFKA-3851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ewen Cheslack-Postava reassigned KAFKA-3851:
--------------------------------------------
Assignee: Ewen Cheslack-Postava
> Add references to important installation/upgrade notes to release notes
> ------------------------------------------------------------------------
>
> Key: KAFKA-3851
> URL: https://issues.apache.org/jira/browse/KAFKA-3851
> Project: Kafka
> Issue Type: Bug
> Affects Versions: 0.10.0.0
> Reporter: Ewen Cheslack-Postava
> Assignee: Ewen Cheslack-Postava
> Priority: Blocker
> Fix For: 0.10.0.1
>
>
> Today we use the release notes exactly as exported from JIRA (see "Prepare
> release notes" on
> https://cwiki.apache.org/confluence/display/KAFKA/Release+Process) and then
> rely on users to dig through our documentation (none of which starts with
> release-specific notes) to upgrade and installation notes.
> Especially for folks who aren't intimately familiar with our docs, the
> information is *very* easy to miss. Ideally we could automate the release
> notes process a bit and then have them automatically modified to *at least*
> include links at the very top (it'd be nice if we had some other header
> material added as well since the automatically generated release notes are
> very barebones...). Even better would be if we could pull in the
> version-specific installation/upgrade notes directly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
