[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: Draft: simple update description guidelines

On Tuesday, 27 January 2009 at 19:18, Rahul Sundaram wrote:
> ---
> * All Updates must refer to a upstream changelog or equivalent if one 
> exists. Otherwise a brief description (a couple of sentence at most) 
> justifying the need for an update must be provided by the maintainers 
> pushing the update.
> * If there are downstream bugs being fixed or intended to be fixed with 
> an update, it must be referred within the update. Maintainers can choose 
> to let bodhi auto close bugs or close it manually as well.

This is redundant. bodhi has a field for bug numbers and it's pretty

> * For security update, add CVE information, if one exists.

As above.

> * It is highly recommended that package maaintainers highlight major new 
> features, critical bug fixes or anything else that has a potential high 
> impact on consumers of your update.
> ---
> Please be specific in your comments and try and be constructive. Thank you.

Nobody reads these anyway, so what's the point? Yum's changelog plugin is
much more useful than this proposal will ever be.


Fedora http://fedoraproject.org/wiki/User:Rathann
RPMFusion http://rpmfusion.org | MPlayer http://mplayerhq.hu
"Faith manages."
        -- Delenn to Lennier in Babylon 5:"Confessions and Lamentations"

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]