How act when bug should be documented in release notes or known bugs
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?
Regards, Adam
--
Adam Tkac, Red Hat, Inc.
--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
05-28-2008, 07:01 PM
Rahul Sundaram
How act when bug should be documented in release notes or known bugs
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?