Comment 6 for bug 557467

Sorry, the message was inadvertently sent before it was finished.

Thierry Carrez wrote on 2010-04-28:

> We cannot push to Lucid a complete new version with new features now,
> though we should fix the critical bugs and the security issues. You
> should open separate bugs about those, since migrating Lucid completely
> to 6.3.16 won't happen at this point, and we'll need separate bugs for
> the Lucid SRU process.

I am definitely:

- not going to help Ubuntu in any way to ship an outdated version (it will
only make users re-report fixed bugs upstream over and over again)

- not going to help Ubuntu help you break out the NEWS file into
individual bugs (I am not reponsible for that the release and package
managers missed to look at the bug in time before the freeze, and sync
   from Debian unstable)

- not going to help in any efforts that are not going to reduce the
upstream support load.

It's not as though recent versions were particularly new or only happened
on the day when you froze the distro.

You're seeingly and deliberately shipping a version that is unsupported
upstream, when a new one was available even before the freeze.

Not taking an up-to-date bugfixed version was instead justified because
there were local changes.

I am not responsible for that relevant parties in Ubuntu fail to look at
bug reports in time. Also, the issue was mentioned on ubuntu-developers@
and -sponsors@ in time before the freeze.

What I will be doing is if the upstream bug reports go out of hand invoke
GPL §2a and demand that the package also be changed and a known old
version has been shipped for reasons entirely at Ubuntu's descretion and
fault.

--
Matthias Andree