Hi,
since we talked about this issue during the DevConf, I’d like to start a discussion about how to tackle this.
Seemingly, some admins do not keep close track of updates. To address the backwardness of those installations and raise awareness for new versions, ILIAS might use an “in-your-face”-approach, to present some reminders to admins, so they update sooner rather than later.
A first option could be, to connect the setup/registration of an installation with an optional subscription to the admin-list. E.g. in the setup’s “Registration”-tab a checkbox could be used to trigger the first registration step with the given client e-mail or an alternative e-mail entered here.
A second option is an alert-box in every admin-GUI, as we already see for the Hotfixes. The box(es) can show information about:
- the current service release to update to
- the current main release to optionally update to
- the end-of-life information, if no new service releases are planned for the present version
To crawl the current releases, cron might be usable, e.g. checking the tags on github. Setting up this job could be a mandatory step during the setup. If current local data from this job is missing because the cron job isn’t set or not working, an alternative alert-box stating something like “CRON-Job not working, see the >> Installation Guide” could appear in the admin-GUIs.
A last option could be to offer a very simple update process, as was asked for here at least for vanilla installations.
What do you think about this and how would you handle awareness? Let's collect some ideas to form an entry for the Feature-Wiki.
Best regards
Christoph