Upgrade notification: Difference between revisions
No edit summary |
No edit summary |
||
| Line 5: | Line 5: | ||
* '''TIME NEEDED FOR IMPLEMENTATION''': 3days | * '''TIME NEEDED FOR IMPLEMENTATION''': 3days | ||
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. | 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 ;-) | |||
Revision as of 20:41, 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
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 ;-)
