...
| Info |
|---|
SSP v2.4.0 Released on 4/24/2014 |
| Warning |
|---|
SSP-2721 is a patch added to v2.4.2 and v2.5.2 to address a bug with the CAS integration for filters/requests. All implementers of this release should consider installing the patches listed in the commit section of the issue details. |
Release Highlights
- Performance Improvement with Person Records
- Action Plan UI Redesign and Multiple Reminders
- MAP Plan Status Calculation Improvements
- MAP Plan Definition to Include Program and Catalog Year
- Early Alert Submission and Response Improvements
- Reset Journal Entry Form after Adding a New Entry
- Service Group Added as Search Criteria
- Message Template Improvements
- Smarter Measure Integration
- 86 bug fixes
Changelog Summary
| Note |
|---|
In progress |
Fresh Installation Instructions
See SSP v2.4.0 Installation Instructions
Upgrade Instructions
| Note |
|---|
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.
| Note |
|---|
In progress |
SSP-Platform Source Code Upgrade
| Note |
|---|
In progress |
...
Upgrading Source Code Forks
See SSP Source Code Upgrade Process
Additional Upgrade Steps
| Warning |
|---|
For all existing installations of 2.0.X and 2.1.X, important upgrade instructions exist in the previous 2.1, 2.2 and 2.3 Release notes.
|
...