This is intentional on my part - it's why I maintain two different trees
of the package (one in Ubuntu proper, one at winehq).
Wine stable releases (even-numbered middle number) have been throughly
regression tested through the Wine release process. Wine alpha/beta releases
(odd-numbered middle number) have not - they're more or less development
snapshots every two weeks.
This means we really don't want to push out a Wine development version
through something like -updates, -backports, or even as a new version in
Jaunty, as for many users it would mean that an "update" actually broke
something they may be depending on.
Having regressions between Ubuntu versions is really bad (in fact it's
our number one complaint), and having regressions after an automatic
update is REALLY bad. In many ways, preventing regressions by actually
testing all the software bundled together is one of our primary jobs as
distro makers.
That said, Jaunty may get a newer version of Wine anyway. However, it will be
one that has been stabilized for a month or so (around beta release) with
various regression patches backported.
** Changed in: wine (Ubuntu)
Status: New => Won't Fix
--
Could you please update the wine version to the latest?
https://bugs.launchpad.net/bugs/314989
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
--
universe-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/universe-bugs
