Right. Another beta version's just been released after another long wait. What's really going on? Is there going to be another 2-month wait for the next one?

Let me start with the dream goal - a definite release cycle, similar to what happens with Ubuntu. I'm not making a promise that phpEdu will (or won't) guarantee a 6-month release cycle but building a user base on such trust and guarantee is worthy of commendation.

This is in the light of the catch-phrase in the FOSS community: it's ready when it's ready. When people dare cough in challenge of that statement, they are always reminded that it's free software, developers donate their time and as such, you can go and place your backside wherever you care to put it. No matter the pros and cons of this philosophy, I'd like phpEdu to implement a definite release cycle, and reach a decision much sooner than later.

Feature creep remains a formidable enemy. Therefore the main priority at this point in time is stabilising the code we've now got and have one more beta version before the first release candidate. The urgent tasks at hand are:

• Reorganise the dashboard
• Fix bugs
• Clean up the code
• Update documentation

A number of features (modules) are in the works but the current code needs tidying up before the project can be taken to the next level.