View Source

h1. Patch Rollout Procedure - OUTLINE


h2. *Patch Rollout:** *{*}DATE*


h3. Patches/Features to be rolled out (table to be filled in):

||  Jira Issue Number \\ || Detail \\ ||
|  SKI-### | Patch description here \\ |

h3. *Pre-Outage Notifications:*

* *CMI2 (Cheryl):** * Update the outage page on Classesv2Docs server (\\classes.yale.edu\classesv2docs\cmi\classesv2\outages\specific.html (or generic.html).  Save document as index.html.  Remember to restore the generic.html as the index.html after outage is over.  (specific.html is the specific-dated outage page, generic.html is the generic outage page.  Either can be adjusted and copied over index.html)  Systems will change the server to point to our outage page at [http://www.yale.edu/classesv2/]).
* *CMI2 (Gloria/David):** * Put a message on MOTD  ([http://research.yale.edu/cgi-bin/cmi/classesv2/workspace/manage_mod.cgi])
* *CMI2 (Gloria/David):** * Notify Sakai team members/Chuck/Departmental Support members of outage window-Departmental Support Members:  [mailto:Matthew.Wilcox@yale.edu], [mailto:Suzanne .Estelle-Holmer@yale.edu], [mailto:Tonie.Young@yale.edu], [mailto:Tolga.Ergunay@yale.edu],[mailto:Ruthanne.Murray@yale.edu], [mailto:Jerry.Honecutt@yale.edu]
* *CMI2 (Gloria):** * Send a note to message@yale.edu
* *CMI2 (Gloria):** * Contact the Help Desk, call 785-3200
* *Michael Appleby:*  Send Change Form to Operations & Unix Systems

h3. *Outage Window Activities:*  DATE

*Testing after the patch:*
* Volunteers needed to 'adopt a tool' for the testing...
*Testing complete:*
* *CMI2 (Gloria, David):** * Change MOTD back to no message.
* *Systems:** * Take down redirect to Classesv2docs page, return to normal login screen
* *Systems:** * Allow logins