| 2010-08-25 12:58:32 |
Chris Coulson |
bug |
|
|
added bug |
| 2010-08-25 12:58:44 |
Chris Coulson |
nominated for series |
|
Ubuntu Lucid |
|
| 2010-08-25 12:58:44 |
Chris Coulson |
bug task added |
|
Ubuntu Lucid |
|
| 2010-08-25 12:59:04 |
Chris Coulson |
affects |
ubuntu |
firefox (Ubuntu) |
|
| 2010-08-25 12:59:26 |
Chris Coulson |
description |
Starting in Maverick, we now send Firefox crash reports directly to Mozilla, using the google-breakpad integration shipped with Firefox. I'd like to switch this on in Lucid for the next security update (scheduled for September 7th).
Unlike other packages in the archive where we aren't particularly interested in crash reports in the stable release (so we disable Apport), Mozilla rely on crash reporting as part of the feedback from testers of their point releases (which we ship). Enabling the crash reporter will hopefully help Mozilla catch regressions earlier, and avoid fire-drill releases like 3.6.8 which are a pain for us.
The change will go in to the staging PPA - ppa:ubuntu-mozilla-security/ppa (today hopefully, as we already have the first spin of 3.6.9). It will sit there for testing until the official release, as with all the other point releases.
The change is pretty low risk (building breakpad, turning on the signal handler in Firerox and shipping the crashreporter binary in the Firefox package).
The crash reporter can be tested with this extension: http://code.google.com/p/crashme/ |
Starting in Maverick, we now send Firefox crash reports directly to Mozilla, using the google-breakpad integration shipped with Firefox. I'd like to switch this on in Lucid for the next point release (scheduled for September 7th).
Unlike other packages in the archive where we aren't particularly interested in crash reports in the stable release (so we disable Apport), Mozilla rely on crash reporting as part of the feedback from testers of their point releases (which we ship). Enabling the crash reporter will hopefully help Mozilla catch regressions earlier, and avoid fire-drill releases like 3.6.8 which are a pain for us.
The change will go in to the staging PPA - ppa:ubuntu-mozilla-security/ppa (today hopefully, as we already have the first spin of 3.6.9). It will sit there for testing until the official release, as with all the other point releases.
The change is pretty low risk (building breakpad, turning on the signal handler in Firerox and shipping the crashreporter binary in the Firefox package).
The crash reporter can be tested with this extension: http://code.google.com/p/crashme/
|
|
| 2010-08-25 12:59:45 |
Chris Coulson |
bug |
|
|
added subscriber Jamie Strandboge |
| 2010-08-25 13:02:53 |
Chris Coulson |
description |
Starting in Maverick, we now send Firefox crash reports directly to Mozilla, using the google-breakpad integration shipped with Firefox. I'd like to switch this on in Lucid for the next point release (scheduled for September 7th).
Unlike other packages in the archive where we aren't particularly interested in crash reports in the stable release (so we disable Apport), Mozilla rely on crash reporting as part of the feedback from testers of their point releases (which we ship). Enabling the crash reporter will hopefully help Mozilla catch regressions earlier, and avoid fire-drill releases like 3.6.8 which are a pain for us.
The change will go in to the staging PPA - ppa:ubuntu-mozilla-security/ppa (today hopefully, as we already have the first spin of 3.6.9). It will sit there for testing until the official release, as with all the other point releases.
The change is pretty low risk (building breakpad, turning on the signal handler in Firerox and shipping the crashreporter binary in the Firefox package).
The crash reporter can be tested with this extension: http://code.google.com/p/crashme/
|
Starting in Maverick, we now send Firefox crash reports directly to Mozilla, using the google-breakpad integration shipped with Firefox. I'd like to switch this on in Lucid for the next point release (scheduled for September 7th).
Unlike other packages in the archive where we aren't particularly interested in crash reports in the stable release (so we disable Apport), Mozilla rely on crash reporting as part of the feedback from testers of their point releases (which we ship). Enabling the crash reporter will hopefully help Mozilla catch regressions earlier, and avoid fire-drill releases like 3.6.8 which are a pain for us.
The change will go in to the staging PPA - ppa:ubuntu-mozilla-security/ppa (today hopefully, as we already have the first spin of 3.6.9). It will sit there for testing until the official release, as with all the other point releases.
The change is pretty low risk (building breakpad, turning on the signal handler in Firefox and shipping the crashreporter binary in the Firefox package).
The crash reporter can be tested with this extension: http://code.google.com/p/crashme/
|
|
| 2010-08-25 13:03:04 |
Chris Coulson |
firefox (Ubuntu): status |
New |
Invalid |
|
| 2010-08-25 13:03:09 |
Chris Coulson |
firefox (Ubuntu Lucid): status |
New |
Triaged |
|
| 2010-08-25 13:03:17 |
Chris Coulson |
firefox (Ubuntu Lucid): importance |
Undecided |
Wishlist |
|
| 2010-08-25 13:05:07 |
Chris Coulson |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2010-08-25 13:22:21 |
Launchpad Janitor |
branch linked |
|
lp:~mozillateam/firefox/firefox-3.6.lucid |
|
| 2010-08-25 15:58:49 |
Chris Coulson |
firefox (Ubuntu Lucid): status |
Triaged |
Fix Committed |
|
| 2010-09-08 18:48:32 |
Launchpad Janitor |
firefox (Ubuntu Lucid): status |
Fix Committed |
Fix Released |
|
| 2010-09-08 19:26:27 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/lucid-security/firefox |
|
| 2010-09-10 08:07:10 |
Muhammad Annaqeeb |
bug |
|
|
added subscriber محمد النقيب |
