Page Comparison

[Note, the fallback release is April 17, 2010]

Personnel:
•    Kirk Alexander
•    Sandra Stewart
•    UC Davis programming team
•    rSmart programming team

Communication
•    server: irc.freenode.net
•    channel: #ucdsakai

During Maintenance Window
Pre Implementation tasks

1. (March 16, rSmart team) check out SAK-3163.patch for Gradebook 2 from our subversion patches director.
2. (March 16, rSmart team) build Release Candidate 1 on smartsite-test.rsmart.com using the SAK-3163 patch.
3.  (March 16, rSmart team) add -Psakai2.6 to the mvn command. This will tell gb2 to build using kernel but not edu-services.Gradebook 2 tag 1.2.0-rc3
   • https://source.sakaiproject.org/contrib/gradebook2/tags/1.2.0-rc3
4. (rSmart team) apply the following patches (to "gradebook" and "gradebook2" modules, respectively):
   • https://source.sakaiproject.org/contrib/gradebook2/tags/1.2.0-rc3/sakai/2-6-x/gradebook-upgrade-1.1.x-to-1.2.x.patch
   • https://source.sakaiproject.org/contrib/gradebook2/tags/1.2.0-rc3/sakai/2-6-x/gradebook2.patch

     No Format
     > cd gradebook > patch -p0 < ../gradebook2/sakai/2-6-x/gradebook-upgrade-1.1.x-to-1.2.x.patch > cd ../gradebook2 > patch -p0 < sakai/2-6-x/gradebook2.patch

5. (rSmart team) If you're starting from a 1.1.4.1 database run the following database script (doesn't include commit statement) – if you're using the same database you used for 1.2.0-b1, then skip this step.
   • https://source.sakaiproject.org/contrib/gradebook2/tags/1.2.0-rc2/sakai/2-6-x/sql/oracle/conversion_1.1.x_to_1.2.x.sql
6. (rSmart team) add the maven environment property -Dsakai2.6 to your mvn alias
7. (rSmart team) ensure that the open session in view filter tags are placed in the web.xml file for GB2
8. (rSmart team) ensure that the servlet being wrapped is the "sakai.gradebook2.dispatcher" servlet THIS HAS CHANGED
9. (March 16, UCDavis team) attach code for duplicate sections fix patch (sak-3144) to RSN: 3986-8306816 ticket.      
10. (March 16, rSmart team) build patch for RSN: 3986-8306816 on smartsite-test.rsmart.com.
11. (March 22, rSmart team) build Release Candidate 2, subversion tag 1.2.0-RC2 RC3 on smartsite-test.rsmart.com
12. (March 29, rSmart team) build Final Release Candidate, subversion tag 1.2.0-RCn RC3 on smartsite-test.rsmart.com

Highlight
yellow color yellow
note:

we may have several gradebook release candidates prior to the production release on April 13.

During the Implementation rollout

1. (5:00am to 5:05 am, rSmart) Place SmartSite into maintenance mode.
2.     (5:05am to 5:20am, rSmart) rSmart will
   1. Check out SAK-3163.patch Final Release from our subversion for Gradebook 2 from our subversion patches director2, tag 1.2.0-RCn.
   2. Build Final Release Candidate  on smartsite-test.rsmart.com using the SAK-3163 patch.Add -Psakai2.6 to the mvn command. This will tell gb2 to build using kernel but not edu-servicesprod.
   3. Retrieve attachment from RSN: 3986-8306816 ticket and apply to SmartSite prod.
3. (5:21am to 5:25am, rSmart) rSmart will bring up one node, still in maintenance mode, for QA verification.

Content and Function Verification Testing

1. (5:21am to 6:00am, UCDavis) QA  will verify that the system has been successfully upgraded by doing the following:
   1. QA test plan tbd
   2. tba
2. (6:01am – 6:15am, rSmart and UCDavis) Team will decide go or roll back.

Vote on our readiness to bring the system back up

1. (6:16am – 6:17am rSmart and UCDavis) Team to vote on readiness to bring the system back up assuming we’re going forward. See rollback section for retreating.

Release the system to public

1. (6:35am – 6:45am, rSmart) bring up all application servers.
2. (6:46 am – 6:47am, rSmart) will release application to public by reapplying normal mode.
3. (6:48 am – 6:50am, UCDavis)  QA/PM will send email notification to our SmartSite community to say the system is back up.
4. (6:50 am – 6:52am, UCDavis) Project or Program Manager will change the MOTD.

Rollback

1. (6:32 am – 7:00 am)      To be determined by rSmart.
   1. (List the first step in rolling back)
   2. list other steps
2. (6:41 am – 6:50am, UCDavis) QA will log in and verify that the fix has been removed by doing the following:
   1. to be determined
   2. to be determined
3. (6:51 am – 6:55 am, rSmart) will bring up the application
4. (6:56 am – 6:57am, rSmart)  will release application to public
5. (6:58 am – 7:00am, UCDavis)  QA/PM will send email notification to our SmartSite community to say the system is back up
6. (6:58 am – 7:00am, UCDavis)   Project or Program Manager will change the MOTD.