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

Re: Fwd: closing out old bugs of unmaintained releases



John Poelstra wrote:
Hello,

Thank you for taking the time to report this bug.  Unfortunately, this
version of Fedora has reach end-of-life and is no longer maintained.
Please refer to  http://fedoraproject.org/wiki/LifeCycle for an
explanation of the Fedora lifecycle policy.

In addition, how about a link to this email-thread explaining why this action is considered necessary (e.g. we need to clear the deck, etc.)?
URL to a wiki entry would we nicer. With some diagrams of the fedora bug process. Words are OK, good pictures better.

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'.

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.

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."

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.

David Timms.


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