View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 174 | Composr | core_upgrader | public | 2010-04-10 23:35 | 2016-01-21 21:52 |
| Reporter | Chris Graham | Assigned To | Chris Graham | ||
| Priority | normal | Severity | feature | ||
| Status | resolved | Resolution | fixed | ||
| Summary | 174: Improved upgrade flow | ||||
| Description | "A new version, 4.1.3 is available. Upgrading to 4.1.3 is suggested by ocProducts due to fixes to browser compatibility. There may have been more important upgrades: read on for the latest recommended upgrade paths." –> "[[Upgrading to at least 4.1.10 is suggested by ocProducts due to a critical vulnerability]]. Browse our <<news archive>> for a full list of the updates or see below for recommended paths." ALSO: spell out all paths in a nice list/table and say when there are no choices. Also add dates of when the recommended upgrade targets were actually released In the upgrade notification block, show the combined upgrade advice of all inbetween versions, rather than just the latest one. Don't link to the news post for a new version from the block, pass the version directly into the upgrader script, and it can fetch the TAR URL automatically as well as show other information from the news post. As a policy ocProducts should make sure download descriptions for new versions are fully updated to mention any upgrade issues that come to light (should not be left in an upgrade issues topic, or news post). However if there is such an upgrade issues topic the download description should link to it (currently just the news post does). Eliminate recommendation to read upgrader tutorial EXCEPT for major/feature releases. Allow setting the 'closed' text from inside the upgrader. Make sure to mention somewhere in the upgrading interface that this process takes 5-15 minutes if nothing goes wrong, but this can easily take longer if you have lots of code/theme modifications - plan in advance; but say "plus backup time" if no recent [<1 day] backup taken (always say what the last backup was or if there was none). Documentation improvements: - Explain in forum tutorial that upgrading a third-party forum without consulting Composr's compatibility is not advisable - Explain in upgrader tutorial that all sites on a M.S.N. should run the same version of Composr (although patch releases can be disregarded in this) - Recommend users create an index.html file for use when upgrading (in case Composr breaks too much to even show a closed site message) and to check it will take precedence over index.php - Explain in upgrader tutorial that minimum requirements, compatibility, or existing functionality (e.g. deprecation) could all change across versions, and that people should not upgrade in haste (except patch releases). | ||||
| Tags | ocProducts priority | ||||
| Attach Tags | |||||
| Time estimation (hours) | 4 | ||||
| Sponsorship open | |||||
