How act when bug should be documented in release notes or known bugs

Rahul Sundaram sundaram at fedoraproject.org
Wed May 28 19:01:03 UTC 2008


Adam Tkac wrote:
> Hi all,
> 
> is somewhere procedure how act when some bug should be documented in
> release notes or on known-bugs page?
> 
> I'm talking about problem in F9 final - when you install bind-chroot
> package (you selected "Install DNS server") bind installation fails
> due no dependency on bind and after installation bind and bind-chroot
> have to be removed and installed again.
> (https://bugzilla.redhat.com/show_bug.cgi?id=446477#c6)
> 
> Update is released but it would be nice to inform users that this
> problem exists and they should not install bind-chroot directly from
> ISO. How should I do it?

The release note process is detailed at

http://fedoraproject.org/wiki/DocsProject/ReleaseNotes/Process

A couple of post release updates have already been pushed out. I am not 
sure we are doing anymore at this point.

Rahul




More information about the fedora-devel-list mailing list