Comment 301 for bug 187313

Revision history for this message
Alexander Sack (asac) wrote :

Philby, the fact that the fix is considered for the stable (security-only) ffox 3.0 branch means that its not considered "low" priority. The importance here on launchpad or bugzilla does not really mean much.

To explain why this fix didn't end up being in 3.0.10

3.0.9 caused a regression that required us to run a firedrill release out of schedule (called 3.0.10); in order to allow a swift release of firefox 3.0.10 all fixes not directly required to address the regression were moved to the next regular release: 3.0.11 - including this fix.