My university has a small problem with Moodle support for older versions. We now are using 2.1.2, and support will end in December, leaving us high and dry for three months. Starting April, the university will probably install 2.3, but our Joho Center has a very strong policy against upgrading in the middle of the year. While of course, there are security fixes which should be implemented, later versions of the same major release do also introduce new features which the university sees as possibily causing conflicts with existing functions.
The Kyoto San-Dai timeline works like this:
- November: Decide on version (usually the most recently released one.
- December-January: Customize the version (outsourced) to add features not available in the off-the-shelf version.
- February - mid-March: testing
- mid-March: Open the new Moodle for teachers to create their courses. (Each year starts with a clean database.)
Now, the current Moodle HQ policy is to supply security patches to versions released within the past 12 months. We hope that we can have the policy were changed to versions released in the past 18 months. Does anyone else have a similar problem with the current policy?