How is the move to a fixed going to affect the update policy? In the past the policy was to support the two most recent stable versions, with a six month release cycle, this which would mean that any given point release would only be supported for 1 year.
However, I note that the updates page (http://docs.moodle.org/en/Updates) states that Moodle 2.0 will be supported till 30 June 2013, a little over 2.5 years after the first release. If I assume that all future releases will be supported for the same period of time, then by Jan 2013 by which time I would expect Moodle 2.4 to be out, then supported releases will be:
2.0 ending June 2013
2.1 ending Dec 2013
2.2 ending June 2014
2.3 ending Dec 2014
2.4 ending June 2015
Is it reasonable to assume that this will be the case? or is the long support period for 2.0 a blip caused by the need to continue 1.9 support for a long period, in which case is the support time likely to shrink back down to a shorter period for each release in order to bring things back in line with prior policy?
I would argue that the minimum period needs to be 18 months, otherwise it is likely that any institution which performs it's upgrades on an annual cycle is going to find itself using an unsupported version for a period of time at the end of the following cycle, assuming that they perform their pre-deployment testing using the current stable release, rather than the development version.