Upgrade notification: Difference between revisions
| Line 18: | Line 18: | ||
* status - 0 (ok), 1 (needs update), 2 (not maintained) | * status - 0 (ok), 1 (needs update), 2 (not maintained) | ||
* end of maintenance dat if known (unix timestamp) | * end of maintenance dat if known (unix timestamp) | ||
* update to version (ex.: 1.9.6) | * update to version recommendation (ex.: 1.9.6) | ||
=Implementation= | =Implementation= | ||
Revision as of 21:18, 5 October 2009
- PROJECT STATE: Proposal, probably to be included in 1.9.x
- MAIN TRACKER ISSUE: MDL-20438
- DISCUSSION AND COMMENTS: n/a
- AUTHOR: Petr Škoda (škoďák) + feedback and ideas from other developers
- TIME NEEDED FOR IMPLEMENTATION: 3days
Overview
The mandatory security measure is to always keep Moodle software up to date. This page describes new mechanism that notifies each admin about available Moodle upgrades. At present upgrade information is available from moodle.org site, we are also sending new version notices via email to registered administrators. Unfortunately many sites are not upgraded regularly :-(
The general idea is that each Moodle instance contacts regularly (every 7 days) moodle.org and fetches the latest version information. Admin is notified by own server when new version available and any new version available. The notification would be also printed on the security overview report, the site notification and the front page (only when admin logged in). Admins would be also notified when branch not maintained any more
The side effect would be that we could get much better version statistics, of course we need to provide opt-out option ;-)
moodle.org side
Simple PHP script which accepts one optional parameter version (ex.:1.9.5) and returns XML file which includes following info:
- status - 0 (ok), 1 (needs update), 2 (not maintained)
- end of maintenance dat if known (unix timestamp)
- update to version recommendation (ex.: 1.9.6)
