The bug fixing will continue on the branch, but there will be no more database changes allowed in 1.6.
HEAD will be freed up again for work on the 1.7 roadmap.
But, in typical Wellingtonian fashion, I celebrated with dinner at The Matterhorn instead.
And it was good.
on the evening a grup called goblin city will perform live !
The signer in flowered shirt is a stragnge guy called Ludo
Taking account of the work necessary to obtain a 1.6 stable version, am I correct if I suppose that the modifications I submitted for these rarely used calculated questions, will be evaluated for the next 1.7 release?
As part of checking the 1.6 stability, I will produce a test extending the one
related to this PHP4-PHP 5 potential language problem in the next days.
The beta should be quite usable now though, for all but big production sites.
Branch tag is MOODLE_16_STABLE
Branch point is MOODLE_16_BETA
Anyway, don't forget to see http://docs.moodle.org/en/Unmerged_files
Let's maintain the status, how many days will we be able to do it?
We all need to do this this in our local dev sites:
cvs -q update -r MOODLE_16_STABLE
and then from now on keep checking 1.6 bug fixes into STABLE first, and then merge them across to HEAD (which is now 1.7 dev).