Table of Contents
SSP v2.3.0 General Release Announcement
| Info |
|---|
SSP v2.3 To Be Released in Mid-March |
Changelog Summary
TBD TBD TBD
Fresh Installation Instructions
See SSP v2.3.0 Installation Instructions
Upgrade Instructions
| Note |
|---|
Very much a work in progress... |
By definition, these instructions cannot provide comprehensive advice for all the situations you may encounter when upgrading source code forks, and they should be understand as a best-effort attempt at a generic recipe for working through any given upgrade, with pointers on known issues and "gotchas" mixed in.
In many cases, a systems administrator with relatively limited SSP-specific experience can successfully execute an upgrade. But again, because upgrading a source code fork almost always involves making decisions about what does and doesn't constitute a valid local change that should be carried forward into the upgraded source code, it may be necessary to involve a developer or technical staff already familiar with SSP internals.
The SSP team strongly recommends a multi-stage process for upgrading institutional SSP installations. Start by attempting the upgrade locally, even in the absence of a complete copy of UAT or production databases. Work out the obvious problems there, then move to your shared QA/Test/UAT/Dev environment and attempt a deployment. You'll usually want to refresh the database in that environment from a recent production backup, if possible, before attempting the deployment. Once everything has been tested successfully in that environment, you should have a very good idea of the exact steps you'll need to reproduce to execute the deployment in production.
SSP Source Code Upgrade
If your deployment is not derived from a fork of the SSP source code project, skip this section and go to SSP-Platform Source Code Upgrade below.
TBD TBD TBD
SSP-Platform Source Code Upgrade
TBD TBD TBD
Additional Upgrade Steps
| Note |
|---|
Thinking I'll try to fold the following advice into the above sections, which I'm imagining will also have pointers to similar documentation in previous release notes. I.e. hoping the above turns into a general recipe with a bunch of individual steps pointing to instructions specific to individual release versions you might be upgrading through. |
For implementers with an existing installation of 2.0.X, 2.1.X or 2.2 the changes described below should be executed after the release is built during the upgrade process.
...