Well I don't think the key point is to be up to the very date, like a rolling release, but update if the newer version is considerably stable and well only add, not cause unstable behaviour.
For example, Libre office right now has two versions on their site: 3.3.4 and 3.4.3 The former is considered more stable, while the other is considered mostly stable. I would think the LTS should always have the former option updated at least every point release of the LTS. Another example would be firefox: currently at 7.0. I would think the best idea for firefox would be to release only after a point/bugfix release is made or it's still running strong after a given point in time (say half the release cycle). Any packages with a LTS source should defiantly not be updated past the LTS version of course, ie the kernel (currently 2.6.32.46). To further my point, I think it probably should only be done on the LTS because the normal releases expect the user to update regularly anyway. I really don't think this is necessary with normal releases. Maybe every point release of the LTS can get a bunch of updates with it? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/578045 Title: Upgrading packaged Ubuntu application unreasonably involves upgrading entire OS To manage notifications about this bug go to: https://bugs.launchpad.net/null/+bug/578045/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
