[6655] in Release_7.7_team

home help back first fref pref prev next nref lref last post

Re: Mail to Intrepid users

daemon@ATHENA.MIT.EDU (Mitchell E Berger)
Tue Mar 30 19:07:05 2010

Date: Tue, 30 Mar 2010 19:06:57 -0400 (EDT)
From: Mitchell E Berger <mitchb@MIT.EDU>
To: Jonathan Reed <jdreed@MIT.EDU>
cc: release-team@MIT.EDU
In-Reply-To: <013A3BF3-5A27-48D3-A867-AD0C70F16268@MIT.EDU>
Message-ID: <Pine.GSO.4.64L.1003301903260.9902@byte-me.mit.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed

Uh, no, that's not the case.  I update it almost daily.  It's loved.
It's just that most people have no clue that it does get this attention.
Do debathena-login machines not count or something?  Otherwise, we
may have a problem, in which case we can probably give you login
access to it to help figure out what's amiss.

Mitch

On Tue, 30 Mar 2010, Jonathan Reed wrote:

> Actually, zsr is not on my list of machines.  Possibly because it hasn't taken updates, and thus never took the counterlog update which allows it to syslog its release codename.    And I bet it's not the only machine that's unloved in terms of updates.   So actually, my user base has increased by 20%, and now only 16.6% of my user base is ready :-/
>
> -Jon
>
> On Mar 30, 2010, at 6:15 PM, Mitchell E Berger wrote:
>
>> I hadn't realized that the number of such machines was so small.
>> Given that that's the case, perhaps I should point out that one
>> of the Intrepid machines (zygorthian-space-raiders) is a machine
>> in the SIPB office that spools music.  The basic reason that
>> it's Intrepid is that nobody pays much attention to taking
>> updates on it other than me, and I figured it was a good idea
>> for SIPB to have a machine running Intrepid during the period
>> it's supported.  We're well aware of the timeline, and I've
>> already talked with Jess Hamrick, who maintains the music software
>> on it, about planning its upgrade during April.  So, there's
>> 20% of your Intrepid user base reporting that we're ready.  8-)
>>
>> Mitch
>>
>> On Tue, 30 Mar 2010, Jonathan Reed wrote:
>>
>>> I'd like to approve a template for contacting users of distributions that are about to get the axe.   Please send me your feedback on this by the end of the week, I'd like to send mail then.  FYI, we have (at the moment), 5 machines counterlogging as 'intrepid'.   There may be more that haven't taken an update since we patched counterlog, but *shrug*.
>>>
>>> Feel free to edit the Hermes stock answer if it's wrong or unclear -- you should all have edit bits if you login to Hermes using certs.
>>>
>>>
>>> /usr/bin/env ANCIENT_RELEASE="Ubuntu 8.10 (Intrepid)" DATE="April 30 2010" CURRENT_RELEASE="Ubuntu 9.04 (Jaunty)"
>>> ----------------------------
>>> To: $USER@mit.edu
>>> From: IS&T Athena Release Team
>>> Subject: Update required for Debathena on $HOSTNAME
>>>
>>> Hello,
>>>
>>> You are receiving this e-mail because you are listed as the moira contact for $HOSTNAME.  This machine is currently running $METAPACKAGE on $ANCIENT_RELEASE.  $ANCIENT_RELEASE will be desupported by Ubuntu on $DATE.  This means that your workstation will no longer receive security updates or bugfixes, so we recommend you upgrade your workstation to $CURRENT_RELEASE as soon as possible.  This upgrade must be performed no later than $DATE -- after that time, it will become _impossible_ to upgrade your workstation.  (This is a limitation imposed by Ubuntu, and unfortunately IS&T has no control over this.)
>>>
>>> Instructions on upgrading your workstation can be found at:  http://kb.mit.edu/confluence/x/TgVa
>>>
>>> As with any software installation or upgrade, we recommend that you have a recent backup of your locally-stored data before beginning the upgrade process.
>>>
>>> If you have any questions, don't hesitate to send e-mail to debathena@mit.edu.
>>>
>>> Sincerely,
>>>
>>> IS&T Athena Release Team
>>> release-team@mit.edu
>
>

home help back first fref pref prev next nref lref last post