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

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

 



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

--
fedora-devel-list mailing list
fedora-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-devel-list

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux