Well, as usual with unrealistic deadlines we're not quite there for 16th September. But we're very, very close, so we've decided to freeze the core code on the DEVELOP branch.

We don't want to have to create a new branch for Dakar, so if you have commit access to DEVELOP branch, please respect this code freeze and follow the following process before checking anything in. The process only applies to the core; directories under twikiplugins are open for checkins as before.

To keep us honest through the next few weeks we (the IRC crowd) have decided to have a Change Control Review Board (CCRB). This is 4 people. For an enhancement to the core code to get through into the codebase between now and DakarRelease, it has to get the support of 3/4 of that board. Bug fixes will go through as usual, but if there is any hint of an enhancement that can't be justified as absolutely required for a main line TWiki release, it has to go to the CCRB.

1. Raise a Bug in Bugs web, classing it as "Enhancement"
2. Mail the url of the topic to twiki-dev, and ask for a CCRB decision
3. CCRB will review, and if they approve will state so in the topic. If 3/4 CCRB members say yes, then it's ago.
4. Unapproved checkins will be reverted.

CCRB members are

• TWiki:Main.WillNorris (Mexico)
• TWiki:Main.LynnwoodBrown (USA)
• TWiki:Main.SvenDowideit (Switzerland)
• TWiki:Main.CrawfordCurrie (UK)

For an enhancement to have any chance of getting in, it almost certainly has to have completed code, documentation and tests. You can branch DEVELOP into the scratch area to do this kind of development. Bugs should be reported in bugs web as normal, and fixes attached as patch files. Bugs web is at http://develop.twiki.org/~develop/cgi-bin/view/Bugs/AllOutStandingItems

The goal is to have it released before WikiSym, but for it to become a full TWiki release it still has to pass the the Peter test, so be careful about commiting sites, especially public sites, to the code.