Hi Tim,

Thank you for reply. I understand that Moodle developers constantly try to keep proper ratio between including new features and improving stability. But this model might be improved to give users a choice.

Once again I recall Debian project, where IMHO stability management is on very high level. Using this analogy,

• 2.0 branch might be 'unstable' where almost everything is possible, new features, not always working
• 1.9 might be testing where new features are introduced, but on terms you mentioned: there is serious reason to do so.
• 1.8 might be stable where only bug and security fixes are possible.

This is real world example that gives users simple to understand message, about what each version can be used for. Moreover this model gives user a choice, between stable, but more or less old, features and more current features but with possibility of problems and experimental package with no warranty at all.

What do you think about this possibility?