I'm very pleased to announce the release of Moodle 2.1, which became available in packaged form from the Moodle download page on July 1, or can be accessed directly from our git repository or one of our CVS mirrors.
This is the first of our releases made with our new development process which emphasises release dates over features. As a result it's right on schedule, but a few features we'd hoped to include were not quite finished in time.
You can read more on the Moodle 2.1 release notes, but the major new features are:
- A whole new question engine (used by quizzes, for example), which makes questions more robust and will enable developers to create all kinds of interesting question types in the future. Some interesting new features like Certainty-Based Marking have also been added. Huge thanks are due to Tim Hunt and Open University for all their work on this.
- Restoring of Moodle 1.9 backups is now possible! Thanks to Moodlerooms for their help in some of the key parts of the core work and to the HQ team for the rest. This was a very complex thing to build due to the many changes between 1.9 and 2.x. Note that only course content in core modules is restored: if you use other activity modules then you need to ask (or help) the developers of those modules to add the new module restore code (thanks to the design this is not a huge task to implement).
- Moodle 2.1 now directly supports mobile apps for some functions. The new Moodle app for iPhone (by Moodle HQ) will be released soon (followed by an Android version later) and these require the secure web services of Moodle 2.1 or later. In addition, there is direct support for mobile-specific Moodle Themes and automatic detection of mobile browsers.
There are many other smaller improvements too, but one of the ones I really like is the new and improved configuration interface for blocks. You should find it a lot easier to understand than the one in Moodle 2.0.
Thanks again to all the developers involved in fixing things large and small in Moodle 2.1 (roughly 100 developers and many more testers). The HQ team will continue working on 2.1.x for a few weeks before starting to concentrate more on 2.2.