Page Comparison

...

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.
4. (March 16, UCDavis team) attach code for duplicate sections fix patch (sak-3144) to RSN: 3986-8306816 ticket.      
5. (March 16, rSmart team) build patch for RSN: 3986-8306816 on smartsite-test.rsmart.com.
6. (March 22, rSmart team) build Release Candidate 2, subversion tag 1.2.0-RC2 on smartsite-test.rsmart.com
7. (March 29, rSmart team) build Final Release Candidate, subversion tag 1.2.0-RCn on smartsite-test.rsmart.com

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.

...

1.     (5:05am to 5:20am, rSmart) rSmart will

   ...

   1. 1. Build Final Release Candidate  on smartsite-test.rsmart.com using the SAK-3163 patch.
      2. Add -Psakai2.6 to the mvn command. This will tell gb2 to build using kernel but not edu-services.

   ...

   1. 1. Retrieve attachment from RSN: 3986-8306816 ticket and apply to SmartSite prod.

   ...

   1. (5:21am to 5:25am, rSmart) rSmart will bring up one node, still in maintenance mode, for QA verification.

   Content and Function Verification Testing
   •    (5:21am to 6:00am, UCDavis) QA  will verify that the system has been successfully upgraded by doing the following:
   o    [QA test plan tbd]
   o   
   •     ( 6:01am – 6:15am, rSmart and UCDavis) Team will decide go or roll back.
   Vote on our readiness to bring the system back up
   •    (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.

   ...