Jerry Amundson wrote:
The particular bug I came upon is upstream[1], but could certainly
apply within Fedora.
I see a few directions that can be taken.
1. The hard line approach - CLOSE it and cite the bug writing
Principles page[2], specifically, "One bug per report". (noticeably
*absent* from bugs.kde.org)
2. Something nicer and, therefore, takes longer...
Thank you for taking the time, blah, blah.
In it's current form, this report is unusable, so...
(Item 1) is a dup of (link)
(Item 2) has been opened as (link to new bz #)
,,,
(Item N) such and such.
3. One or another variation of 2.
Thoughts?
jerry
[1] http://bugs.kde.org/show_bug.cgi?id=171832
[2] https://bugzilla.redhat.com/page.cgi?id=bug-writing.html
Not quite following you here is this for a report that has been filled
in bugzilla or a report
that you found in a upstream bugzilla?
Usually bugs get closed with a link to the report upstream if they have
been reported upstream.
( I think that is if the upstream maintainer is not within the Fedora
community )
And if i'm not mistaken I think the KDE maintainers that are within the
Fedora community wants
bugs against KDE in Fedora rather to be filed upstream instead of Red
Hat's bugzilla.
Kevin can correct me if i'm mistaken here..
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-test-list mailing list
fedora-test-list@xxxxxxxxxx
To unsubscribe:
https://www.redhat.com/mailman/listinfo/fedora-test-list
