F10 packages for the firefox security update
Christopher Aillon
caillon at redhat.com
Thu Nov 13 21:31:51 UTC 2008
Jesse Keating wrote:
> On Thu, 2008-11-13 at 15:37 -0500, Christopher Aillon wrote:
>> Needing to be tagged for F10 final are:
>>
>> xulrunner-1.9.0.4-1.fc10
>> firefox-3.0.4-1.fc10
>> seamonkey-1.1.13-1.fc10
>> epiphany-2.24.1-2.fc10
>> epiphany-extensions-2.24.0-2.fc10
>> azureus-3.0.4.2-18.fc10
>> blam-1.8.5-4.fc10
>> devhelp-0.21-3.fc10
>> evolution-rss-0.1.1-4.fc10
>> galeon-2.0.7-3.fc10
>> gecko-sharp2-0.13-2.fc10
>> gnome-python2-extras-2.19.1-24.fc10
>> gnome-web-photo-0.3-12.fc10
>> google-gadgets-0.10.1-5.fc10
>> kazehakase-0.5.6-1.fc10.1
>> Miro-1.2.7-2.fc10
>> mozvoikko-0.9.5-4.fc10
>> mugshot-1.2.2-3.fc10
>> pcmanx-gtk2-0.3.8-3.fc10
>> ruby-gnome2-0.18.0-2.fc10
>> yelp-2.24.0-3.fc10
>
> I hate to ask this, but how much testing has these packages gotten?
I get embargoed source code 10-14 days in advance that I've been running
local builds with for xulrunner, firefox, seamonkey, epiphany, mugshot,
devhelp, and yelp, and the equivalent RHEL builds have had ample
testing. And of course, Mozilla upstream's test process makes
everything else look completely untested by comparison.
But because we have no way of doing embargoes in Fedora land, almost all
testing has been on builds that are not these exact bits since I could
not do anything in Fedora until last night. I am running F-10 though,
so they have slightly more testing post-build than the F-8 and F-9
builds which are going out.
More information about the rel-eng
mailing list