Comment 5 for bug 557467

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)

- help you

I am not going to clone/file separate bugs for each of the relevant NEWS
entries.

I am not going to help you ship an outdated version.

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

with all the fixes I have neither interest nor resources to do so. Do
update.

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

1. Newer releases have been available for long enough, both directly and
through Debian, particularly before the freeze.

2. Relevant pointers have been filed to the Launchpad Bugs section soon
enough before the freeze.

3. I am only supporting the latest upstream release.

--
Matthias Andree