[DC LoCo] Double Double MOTD bug

[Ken Stailey]

--- On Mon, 6/6/11, Ted Smith <teddks at gmail.com> wrote:


> I'm shocked and appalled that Canonical is screwing over
> their users and
> the entire GNU/Linux community by ignoring such a critical
> issue. How do
> they expect us to get beyond 3% market share without a
> working /etc/motd!? This is worse than when pulseaudio
> killed my dog.

In the last four weeks the supposedly-stable LTS platform had

/etc/motd.tail overwritten with garbage

cron killed (how many servers out there ceased getting updates moving forward because they haven't rebooted and cron is no longer running)

/etc/motd.tail overwritten with garbage a second time.

Are we certain that if painfully obvious blunders were pushed out as purportedly-stable updates that more subtle things have not been broken as well?

Based on appearance the QA process goes:

1. Put an update in a proposed queue.

2. Ask people to test the proposed package but do no testing of your own.  This is apparent based on the three QA failures in listed above.  Surely anyone who installed a copy of Ubuntu LTS server in a VM and then put the updates on and logged it would see there were problems.  But that must be way to much work.

3. In the absence of evidence (i.e. no complaint reports) blindly push the update out onto all LTS "stable" systems that are receiving updates.