A separate page provides information about using CommonSpot V6 for classic pages.
This page is about the upgrade process, from a content contributor's or subsite pagemaster's perspective.
The overall sequence of events was as follows:
Authoring freeze during copy from production to test.
Perform standard upgrade on test.
Confirm that our local customizations are functioning correctly.
OIT staff experiment and document (creating pages such as this and the linked pages) -- the test servers may be taken offline with no notice during this phase.
Initial user testing: one-on-one sessions with Web Services staff for select volunteers (content changes cannot be transferred back from test to production) -- the test servers should be more stable during this phase, but some ongoing work may require authoring freezes or other disruptions.
General experimentation for content contributors and subsite pagemasters (content changes cannot be transferred back from test to production) -- the test servers should be even more stable during this phase, but some ongoing work may require authoring freezes or other disruptions.
Freeze authoring on both test and production; upgrade the production authoring server and the new backend database while keeping all of the production ROPS online, so that CommonSpot pages on www.ohio.edu are visible (this is started "dark and early" on Monday, December 12, and lasted 48 hours); take the ROPS offline and upgrade them (during this time a temporary "outage" page was displayed if any CommonSpot page was requested -- it included links to non-CommonSpot services -- this was finished and the ROPS back online by 8 am, and we restored authoring under V6 Wednesday afternoon, December 13.
All subsite pagemasters and content contributors should have tried out V6 during phase 6, both for overall familiarization (to be able to work more efficiently after the upgrade) and especially to check anything that you figured out on your own, that wasn't already documented in the V5 pages linked from the secondary navigation block at the left (we documented for V6 all the things that we had documented for V5; we probably caught most of the issues with those features in the process).