Comment 17 for bug 954496

When Miro 5 makes it into later versions of Ubuntu, we can backport it to precise as a backport. You can use the requestbackport tool in ubuntu-dev-tools to request that backport when appropriate. That tool will let you know the level of testing required for the backport (install/run for itself and its reverse dependencies). We generally don't push major new versions into a stable release except for the backports pocket as it's difficult to be sure that the new version won't introduce more bugs than the old one had. Backports is opt-in, so if a user would like a newer version of an application, they can try it. The purpose of backports though is for new features, not to fix bugs. A targeted fix as a Stable Release Update is much more likely to fix the issue at hand without causing other issues (that's why there's a verification period in the proposed repository).
Miro is not directly supported by anyone in Ubuntu; that is, there is no one specifically claiming to support it. Anyone may propose bug fixes assuming they meet the Stable Release Update criteria. LTS in this context refers how long the core infrastructure for the release will be supported (mainly for security updates).