@DJ_Peng Hardy will be a LTS, so there had to be made a decision, which version to include. A stable but soon outdated version of firefox, or a new version (and therefore upstream activly maintained version), that will be finished within the next few weeks (and these changes will be made available for hardy, even if the final firefox will be released after hardy).
So I think, this was the better solution, because a lot of people would complain about hardy shipping an "outdated" browser and the trouble with backporting security-patches to the 2.x line, which will a few months after 3.0 release no longer be maintained upstream. -- Update to 3.0 beta 4 https://bugs.launchpad.net/bugs/201839 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
