but that was last year and things have changed a lot since then, according to the Moodle 2 planning document which I have been following very closely recently. While some elements are 95% done, some are only 5% done. I'v been informed on a number of occasions with confidence (by people who aren't following the document, I suspect) that "Moodle 2 will be out at the end of the year" Well, as we are not even in beta yet I find that hard to believe -so is anyone prepared to give a clearer answer? Or do these people know something I don't know?
Many thanks
At present, I'd guess there might be a beta in the northern hemisphere's Spring 2010. (Meaning final release could be in summer depending on how the beta goes.)
This guess is definitely subject to change. (Probably more likely to change to 'later' than 'earlier', from recent experience.)
Or to put it another way...
When it's ready!
--sam
PS Just in case it's unclear, I am not part of the Moodle HQ team, so this guess obviously has no official status whatsoever.
Community hub - Jerome is actively developing it now, and I don't see this holding up the beta.
Course Completion & Progress tracking - I am sure catalyst will have this done before everything else is. I just read the spec, and it looks good to me.
Secure RSS feeds - Will get finished no problem.
Backup 2.0 & IMS CC - Big Job for Eloy. Glad I don't have to work on this . This probably is one of the rate-determining steps.
Site-wide groups & Enrolment improvements - This is the one that worries me. I quite agree with Petr that there is a mess here that needs to be sorted out. However we still don't have a detailed plan, it is a fairly big job, and as ever there are lots of other things for Petr to work on. My vote is to live with the current mess until 2.1 (including doing a bodge job implementation of site-wide groups) so we can release Moodle 2.0 sooner.
Move grading to gradebook plugins - same as for enrolment changes. There is a mess here that needs to be cleaned up, but I would rather see an earlier 2.0, and live with the current mess until 2.1.
Navigation/Blocks/Pagelib 2.0 & JavaScript cleanup - This is what I was working on up until I left Moodle HQ, and Sam Hemelryk and Nicolas have picked up the baton and are running with it. Thank guys. Like backup, this could be another thing that controls how soon we can get to beta.
Text formats as plugins - Needs to be done before beta. Should not be a problem.
Wiki 2.0 - I don't know what is happening here, but I know it is waiting for some of the other things like text formats.
Lesson 2.0, My Moodle - Similarly, I don't know. However these are being done by non Moodle HQ people, so I guess that either they happen before the beta and are included, or get delayed until 2.1.
I think that if we control the scope, then it is still possible to get to beta this year. And I think that all developers should be working towards getting their beta work done before Christmas.
Then, like 1.9, expect a 3-5 month beta period, hopefully with things like a bugathon to encourage lots of people to participate in testing and bug fixing.
Anyway, that is my best guess.
Thanks Tim.
Still, we'll see
And if you do a release with just internal API rework, incompatible with contrib stuff, and no new features... nobody uses it. (Ask apache folks ).
So I keep lighting candles for the Moodle HQ guys...
Yes, me too. I'm hoping for great things
I am all for small steps, but it is a fact that most of the internal API rework what's happening in 2.0 cannot be done in small steps.
Absolutely agree.
Moodle 1.9 is a strong release. There have been a lot of features over the last few releases, often making fundamental changes to the way teachers use moodle (e.g. roles/grades/groups). Giving our our users some time to feel comfortable with what they have now is not necessarily a bad thing.
Lets not forget the thousands of teachers around the world who are just getting to grips with Moodle in small steps. These users are likely to be unrepresented in the moodle.org community (due to its nature) but are still important.
I also don't think that missing another 'academic year' is necessarily a bad thing. With such large API changes the longer release cycle also helps those managing moodle deployments to have time to prepare. We should try and get our documentation (and API stability) to the stage that these people can be preparing their plugins and customisations to deal with the API changes early - some of this work is likely to be significant and when Moodle 2.0 is released the pressure will be on to deploy it ASAP. If people are working on getting their customisations ready early we can also exploit more early testing.
Still, as soon as I hear 'bugathon' being yelled from the southern hemisphere I will update my Git repo and get stuck in.
I am about to attend a meeting where I am going to ask for some of my work hours to be given over to help with the Moodle project.
I have been working with our own custom site-wide groups code for a couple of years now and would like to offer my programming skills to help get the enrolment / site-wide groups part of Moodle 2 working.
Is there anything I could do to help? I am happy to programme to someone else's requirements.
Sincerely,
Dan Ballance
Royds Hall High School,
Huddersfield
West Yorkshire
UK.
The roadmap and spreadsheet is the best way to keep up. I have some pending updates to make there, so keep an eye on that.