Martin Dougiamas

Please note that our PULL process for reviewing code for integration has changed.

The workflow for pulls has now been integrated into the main workflow for MDL issues, and is no longer a separate PULL project in the tracker.

The main benefits of this are keeping it simpler for users, and reducing the problems of discussions being spread across multiple places.  Viewing the History tab will give you a complete history of the issue, including failed PULLs.

For more details about the new workflow see http://docs.moodle.org/en/Development:Process in Moodle Docs.  It's still being tweaked/improved too so please let me know of you find any problems.

We have just branched MOODLE_20_STABLE in git.

Since the 2.0 release last November, we at Moodle HQ only been working on the stable 2.0.x series, so it was a lot easier to stay on the master (HEAD in the old terminology) to reduce the amount of work needed to get new code into git.  However, we are now starting work on 2.1 features, so the 2.0.x branch has been split away (at the end of last week).

For the next week or so at least the two branches will remain the same, so you have some time to deal with this, but if you are using git (or CVS for that matter) to maintain your stable sites, then you should make sure they are updating from the MOODLE_20_STABLE branch.

Even if you do accidentally update from the master/HEAD unstable version in future, a new feature in Moodle 2 (thanks David!) will actually warn you that you are about to upgrade to an unstable version and give you a chance to fix the problem.

Finally, what this means for developers is of course that you need to file three separate pull requests for most patches:

• 2.1 (master)
• 2.0.x (MOODLE_20_STABLE)
• 1.9.x (MOODLE_19_STABLE)   (if applicable)

I'm still working on simplifying this process in the tracker.

Just a heads-up for everyone, we resolved yesterday that Moodle 2.1 will *require* PHP 5.3 as a minimum.

1) Because PHP 5.2.x is no longer supported by php.net

2) So that developers can start relying on some of the new features introduced in PHP 5.3.  (Note, we still recommend 2.1 fixes be written in a way that's easy to port back to 2.0)

Hi Mary!  I just updated the page in Docs a bit, hope it's clearer!

They are really a very rough progression, obviously, but by structure I meant that yes, you could start giving students more editing rights and more control over what is in the course.

Hi Ian,

Not shouting at you but just to gently correct your surmise about Moodle Partners and forums ...

One of the main advantages of being Moodle Partners is that they have direct priority support from us at Moodle HQ, via our helpdesk, the tracker and instant messaging, so they have no need to ask for technical support in the forums.  They are not "distant" from core development by any means, in fact a lot of them are involved in the roadmap.   Regardless, a lot of them do get involved in the forums anyway because they want to be involved in the wider community.

And of course the Moodle Partners themselves offer support contracts directly to their clients (including many many corporate clients) direct by phone, email and other means.

As such I can't see an "issue", as you put it.

Cheers!