I have a query in relation to CMS support lifecycles. One of our partners uses a legacy version of concrete5 to maintain there website, who issued an end-of-life announcement last month:
The note does clearly say that critical security updates will still be applied for a further 12 months, but I want to identify the risks in using this at present. Apart from 'critical updates' what other types of support/update would you receive if you move to a supported version of the software, that they will be missing out on while still operating the legacy version? I would like them to be more reactive and rather than wait right up until the end of the 12 month period, and upgrade now to a supported release, but I need some more examples of why this is required at this stage/what they are missing out on/risks in using the legacy version.