Keeping browsers updated on previous Ubuntu/armel releases

Registered by Alex Chiang on 2011-10-14

How can previous armel releases of Ubuntu stay current with modern browsers, to receive regular security and feature updates? The current backports in PPAs have x86 builds, but not armel; thus there aren't any easily accessible versions of these browsers even though the majority of the hard work has already been done. Canonical's OEM team regularly suffers from this pain, although there are likely other communities who could also benefit from this work.

Blueprint information

Status:
Not started
Approver:
None
Priority:
Undefined
Drafter:
None
Direction:
Needs approval
Assignee:
None
Definition:
New
Series goal:
None
Implementation:
Unknown
Milestone target:
None

Related branches

Sprints

Whiteboard

micahg 2011-10-17 - From the security team's perspective, we try not to have regressions in armel when updating the browsers with security updates. Armel is an officially supported arch from Lucid on. Chromium, which technically isn't officially supported by the security team, has been an exception due to the long build time and the desire for quick turnaround. I think this issue has been solved by the new panda armel builders. So, we're left with new versions. Chromium already gets the latest release, so I think the question here is Firefox. We're waiting to see what happens with the upstream plans for an LTS release for Firefox. Non-LTS Ubuntu releases will stay on the rapid release train regardless.

jrp 2011-10-17 - I know for Lucid there are plans for a Chromium 14 build in November... but right now the version available is Chromium 10. So I understand the "already gets the latest release" part is still a work in progress.

(?)

Work Items

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.