Mark McLoughlin wrote:
<snip>
.....
<snip>
I think a sensible policy is:
1) File the bug against the version you have tested with
2) If this version is not rawhide, there is generally no need to also
file a bug against rawhide. Maintainers should always check
whether the bug is fixed in rawhide. Commenting whether you
believe the bug exists in rawhide is always useful.
3) If you think this is a critical bug and have checked that it
exists other released versions, then you should clone the bug for
those other versions.
4) Otherwise, just comment on the impact to other versions and let
the maintainer decide whether cloning the bug is appropriate.
I do believe you nailed this one Mark :)
+1
No, it's not a black/white policy. It requires a little bit of common
sense. But that's okay, right?
Of course not and alternative, different approaches,
better suggestions/solution are always welcome.
JBG
begin:vcard
fn:Johann B. Gudmundsson
n:Gudmundsson;Johann B.
org:Reiknistofnun - University of Iceland;IT Management
adr:Taeknigardi;;Dunhagi 5;Reykjavik;;107;Iceland
email;internet:johannbg@xxxxx
title:Unix System Engineer RHCE,CCSA
tel;work:+3545254267
tel;fax:+3545528801
tel;pager:N/A
tel;home:N/A
tel;cell:N/A
url:www.rhi.hi.is
version:2.1
end:vcard
--
fedora-devel-list mailing list
fedora-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-devel-list
