Implementation Plan, September 30, 2006
- Former user (Deleted)
Jira Reference |
Summary of Tasks or Story |
Steps |
Resource Commitments |
|---|---|---|---|
Sak-112 |
Message Center performance improvements and bug fixes |
Wednesday Steps |
|
 |
 |
Confirm with QA that Message Center performance and bug testing is released for production roll out. |
Code Migration team: Emily, Thomas, Sandra, Jon, and Pat |
 |
 |
Review QA's comments entered into Jira tickets from testing. |
Thomas |
 |
 |
Notify DBA (Geeta and Prabhu) of their involvement and determine their availability during the Saturday roll out. |
Thomas and Emily |
 |
 |
Notify system administration of their involvement and determine their availability during the Saturday roll out. |
Thomas and Emily |
 |
 |
Notify Communications (Michael G.) that there will be production activity this weekend. |
Sandra and Kirk |
 |
 |
Friday Steps |
 |
 |
 |
Compile all source code and check files into Subversion? |
Thomas and Emily |
 |
 |
(other Subversion steps getting things ready for prod) |
Thomas and Emily |
 |
 |
Notify System Administration of expected downtime. |
Thomas and Emily |
 |
 |
Compile list of functional changes to Message Center that will be made available via the expected roll out. Provide this list to Communications to announce to SmartSite customers. |
Sandra |
 |
 |
(other things for Friday – what are they?) |
 |
 |
 |
Saturday Steps |
 |
 |
 |
Check out source from Subversion? |
Thomas and Emily |
 |
 |
Shut down system if necessary. |
Thomas and Emily |
 |
 |
Copy executables to SmartSite production. |
Thomas and Emily |
 |
 |
Bring system back online. |
Thomas and Emily |
 |
 |
Notify Sandra and Kirk that the installation is complete. |
Thomas and Emily |
 |
 |
Log onto system and exercise Message Center's new functionality |
Sandra and Kirk |
 |
 |
Report any unexpected behavior if observed. |
Sandra and Kirk |
SAK-203 |
Have SmartSite.ucdavis.edu point to our Sakai production server. (How is this to coordinate with the skin change in SAK-221?) |
Wednesday Steps |
 |
 |
 |
Confirm with QA that SmartSite Host name testing is released. (Actually, I don't know how this will be tested. Maybe there is a test DNS server.) |
Code Migration Team |
 |
 |
Review QA's comments entries in Jira ticket. |
Don't know. Who is this? |
 |
 |
Notify Data Center of their involvement and determine their availability during the Saturday roll out. |
Thomas and Emily |
 |
 |
Notify System Administration ( and John Harris?) of their involvement and determine their availability during the Saturday roll out. (Not sure who makes the entries in DNS.) |
Emily and Thomas |
 |
 |
Friday Steps |
 |
 |
 |
(Don't know what goes here for this task.) |
Don't know. Who is this? |
 |
 |
Notify System Administration of expected downtime. |
Thomas and Emily |
 |
 |
Write up changes for SmartSite Host Name Server changes expected for the production roll out. Provide this to Communications to communicate with SmartSite customers |
Sandra |
 |
 |
(Other Friday things go here. What are they?) |
 |
 |
 |
Saturday Steps |
 |
 |
 |
Make the changes to DNS |
Don't know. Someone at the DC? |
 |
 |
Notify Sandra and Kirk that the installation is complete. |
Thomas and Emily |
 |
 |
Log onto SmartSite and verify that SmartSite.ucdavis.edu goes to our production server. |
Sandra and Kirk |
 |
 |
Report any unexpected behaviour if observed. |
Sandra and Kirk |
SAK-197 |
Support and Training tool button should appear on all new course and project sites. This is a change to the batch course create programming. |
Wednesday Steps |
 |
 |
 |
Confirm with QA that adding the Support and Training tool button programming change is released for production roll out. |
Code Migration Team |
 |
 |
Review QA's comments entries in Jira tickets. |
Thomas |
 |
 |
Notify DBA (Geeta and Prabhu) of their involvement and determine their availability during the Saturday roll out. |
Thomas and Emily |
 |
 |
Notify System Administration of their involvement and determine their availability during the Saturday roll out. |
Thomas and Emily |
 |
 |
Notify Communications that there will be production activity this weekend. |
Sandra and Kirk |
 |
 |
Friday Steps |
 |
 |
 |
Compile all source code and check files into Subversion? |
Thomas and Emily |
 |
 |
(other subversion steps for Saturday roll out) |
Thomas and Emily |
 |
 |
Notify System Administration of expected downtime. |
Thomas and Emily |
 |
 |
Compile list of functional changes to Course Create Program that will be made available via the expected roll out. Provide this list to Communications (Michael G.) to communicate with SmartSite customers. |
Sandra |
 |
 |
Saturday Steps |
 |
 |
 |
Check out source from Subversion? |
Thomas and Emily |
 |
 |
Shut down system if necessary. |
Thomas and Emily |
 |
 |
Copy executables to SmartSite production |
Thomas and Emily |
 |
 |
Bring system back online. |
Thomas and Emily |
 |
 |
Run batch create program to creat new course sites and verify that course sites are created with the link to Support and Training site. |
Thomas and Emily |
 |
 |
Notify Sandra and Kirk that the installation is complete. |
Thomas and Emily |
 |
 |
Verify that the new course sites have been created with the link to Support and Training site. |
Sandra and Kirk |
 |
 |
Report any unexpected behavior if observed. |
Sandra and Kirk |
SAK-221 |
Skin changes for new login / logout and Menu Roll-over (How is this to affect SAK-204?) |
Wednesday Steps |
 |
 |
 |
Confirm with QA that skin changes for new login / logout and Menu Roll-over testing is released for production roll out. |
Code Migration team |
 |
 |
Review QA's comments entries in Jira tickets. |
Thomas |
 |
 |
Notify DBA (Geeta and Prabhu) of their involvement and determine their availability during the Saturday roll out. |
Thomas and Emily |
 |
 |
Notify System Administration of their involvement and determine their availability during the Saturday roll out. |
Thomas and Emily |
 |
 |
Notify Communications that there will be production activity this weekend. |
Sandra |
 |
 |
Friday Steps |
 |
 |
 |
locate skin files and consolidate them in Subversion. |
Thomas, Emily, and Simon |
 |
 |
(other Subversion activities go here) |
Thomas and Emily |
 |
 |
Notify System Administration of expected downtime. |
Thomas and Emily |
 |
 |
Compile list of functional and observable changes to the SmartSite skin that will be made available via the expected roll out. Provide this list to Communications to communicate with SmartSite customers. |
Sandra |
 |
 |
(other things for Friday) |
 |
 |
 |
Saturday Steps |
 |
 |
 |
Check out skin files from Subversion |
Thomas and Emily |
 |
 |
Shut down system if necessary |
Thomas and Emily |
 |
 |
Copy skin files to SmartSite production |
Thomas and Emily |
 |
 |
Bring the system back online. |
Thomas and Emily |
 |
 |
Notify Sandra and Kirk that the installation is complete. |
Thomas and Emily |
 |
 |
Log onto SmartSite, observe and exercise new skin changes. |
Sandra and Kirk |
 |
 |
Report any unexpected behavior if observed. |
Sandra and Kirk |