>Over the past couple of years, Moodle has been on a path to a rapid release cycle for their software releases which in many ways is on the scale of being both good and bad.

The general pros of this approach, besides the the newer features and a host of minor impovements, is that everything has been built quickly on the previous release. This is great for users that may have previously found a particular aspect of Moodle a source of frustration that has now been fixed for whatever reason. Visually not much will change so consistency is never a big deal as there are never any massive changes.

For me however, the cons massively outweigh the pros.

Cons – catastrophic unreliability. Ok that sounds dramatic and it probably isn’t true anymore but I’ve written that there for a reason, because it could happen. When I was testing to upgrade to Moodle 2.0, nothing, and I mean nothing worked. It was awful. Not even reluctantly I stayed with 1.9 for at least two years after Moodle 2.0 was released and by that point 2.3 was with us. This also didn’t work properly until the first minor point release of 2.3.1 which was exactly where I saw my opportunity. I went with this and ran into other problems that I hadn’t forseen (have a look through my previous entries). Other cons that come with a new release is the fact that you potentially now have new features that users are no longer used to, or perhaps the functionality is no longer the same.

For me personally, the unwritten (and now written rule) is that you shouldn’t update mid-year. For your own sanity, wait until at least the first minor point release where everyone else has deployed and found / fixed a good quantity of bugs in there. 2.5.x has been very stable for me so far and I probably won’t be upgrading to 2.6/.7/.8 or whatever is out come July / August time next year.

Tread carefully if you want to go to Moodle 2.6. For the brave out there, here is the link to the download.