David,
Sounds like a good thing entering it into Bugzilla, however, if there is
not a priority within Red Hat to fix it, the bug will sit there and rot...
Might be a good time to split the bugzilla between active devlopment and
legacy, and move the bugs over as needed, where they can be triaged, and
dealt with in accordance with the Fedora Legacy charter.
Thoughts?
Tim
At 01:57 AM 10/6/2006, David Eisenstein wrote:
FOLKS: PLEASE HELP US OUT!!
Chen, (and anyone reading this): you can help us by opening Legacy
Bugzilla reports on security issues that you are concerned with or
know about.
Bugzilla is the tracking system that we use to track security issues with
our packages, from initial awareness of the issue to creating test RPM pack-
ages, doing testing/QA'ing on source and binary packages, to releasing pack-
ages to Legacy's official updates, which your yum updates can pick them up
from. A fairly decent Bugzilla ticket to look at that illustrates the
process is here:
<https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=189672>.
There is an old saying, "If it's not in Bugzilla, it's not a bug." Those
of us who work with building and testing packages are not aware of issues
until they're entered there or mentioned here on this list. We can use
as much help as we can get, and opening Bugzilla's is a pretty easy way
to help us out.
--
"Do not dwell in the past, do not dream of the future, concentrate the mind
on the present moment."
-Buddha
--
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.408 / Virus Database: 268.13.1/470 - Release Date: 10/10/2006
--
fedora-legacy-list mailing list
fedora-legacy-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-legacy-list
