[19372] in Hotline Meeting
Re: Steps/Process for a Patch release
daemon@ATHENA.MIT.EDU (Kimberly Carney)
Thu Oct 28 14:26:07 1993
To: basch@MIT.EDU, mhbraun@MIT.EDU
Cc: tjm@MIT.EDU (Tim McGovern), release-76@MIT.EDU, athena-outage@MIT.EDU,
In-Reply-To: Your message of Thu, 28 Oct 93 13:07:14 -0400.
Date: Thu, 28 Oct 93 14:25:04 EDT
From: Kimberly Carney <kim@MIT.EDU>
I suggested to Tim that we use <athena-outage> because it contains
the front-line support groups: cfyi, hotline, f_l's, etc... I made
the assumption that we'd have relatively few critical bug fixes,
thus traffic would be low.
I agree that it's important to keep the bandwidth to noise ratio low
on <athena-outage>. Let's use the <athena-outage> list for only
a limited set of announcements, and use the release mailing list
for most of the traffic. Interested parties can always subscribe
to the release list or read the discuss meeting. Below are the
revised steps of the process.
Thanks for your suggestion.
Kim
=> 3. rel-eng or ops sends mail to <release-nn@mit.edu> to inform
=> everyone that a fix has been found, and deployment is imminent,
=> although a schedule may not have been set as yet. At this stage,
=> all of the affected groups need to be bought in to the deployment.
=>
=> 4. ops sends mail to <athena-outage@mit.edu> indicating that
=> a fix will be deployed, and the schedule.
=>
=> 5. ops sends mail to <release-nn@mit.edu> when the deployment
=> has been completed.
