On Sat, 2008-01-05 at 22:20 +1100, David Timms wrote:
>> We therefore regret the necessity of closing this bug report
WONTFIX.
Regret is a bit much!
'We will be automatically closing this bug report as WONTFIX'.
-1. In some cases, unfortunately, any message may be the first (or the
first in a long while) seen by the reporter, and it would be nice not to
tick that person off with the first twitch of life in a while. :-)
>> Please upgrade to a currently maintained release of Fedora,
currently
>> either Fedora 7 or Fedora 8, and attempt to reproduce this bug. If
>> the bug still exists, feel free to re-open this bug report, changing
>> the version accordingly, or file a new bug report (you can use the
>> 'Clone as Bug' link at the top of this bug report in order to preserve
>> the content of this bug in the new one).
>
> s/'Fedora 7 or Fedora 8'/'Fedora 8 or rawhide' My hunch is that if
> someone says "this is still broken in Fedora 7", a developer would
> naturally ask next, "how about in Fedora 8 or rawhide?" Save them a
> step and some frustration.
John: I understand what you mean, but in the general case, would it be
fair to say:
"We suggest, if you have not already done so, to upgrade your Fedora
installation to a currently supported release [7 or 8], and use pup or
yum to update Fedora to the most current updates.
If we're asking the user to upgrade to a stable release, it should be to
the release for which they have the longest window of time before having
to upgrade again.
It would be helpful to the Fedora project if you are then able to
re-test this issue with the newer release, and note in a comment on this
bug report whether you found the issue solved [and change it to CLOSED -
CURRENT_RELEASE with the version number] or still present.
If the bug is still present, there may also be a newer development
package that you could test, available in the development repository.
{see wiki for how to yum --enablerepo=devel update this_package}. Again,
entering a bugzilla comment to say you tested with that rawhide version
and the result of your test, and including a change in bug resolution to
CLOSED - NEXT_RELEASE helps developers to make progress on the issue you
found."
Hmm. I wonder how many will take us up on that offer, have a problem
due to instability of other bleeding-edge stuff brought in as
dependencies, and then write us off. I'm not saying it's a bad idea to
ask reporters to do it, but we should be up front about the
ramifications.
I think that it might also be useful to encourage people to state
they
no longer have hardware specific to a bug if that is the case.
+1.
--
Paul W. Frields, RHCE
http://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
Fedora Project:
http://pfrields.fedorapeople.org/
irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug