For anybody who is not in #openclonk-dev regularly, here is a short status update:

The only thing that is missing for a working release now is a working update system. It is almost finished: If the C4Version.txt in the repository gets updated, the build scripts are automatically notified, the build scripts in turn pull the newest repository changes, compile the engine, build the installation files plus the C4U update files and upload them to the openclonk website. The engine then fetches the update package when the masterserver's version information has been updated (currently: manually) and installs them. The system works so far, only the application of the c4group update packages fail on Windows 7 (which, by the way also exists for Clonk Rage) amongst some other smaller issues. See the bugtracker.
Additional features that are planned but not implicitly necessary for a public release are: Automatic creation of linux installation files and updates and even more automation in the update process.

The release will delay a bit because of that. But we can already now enter the testing phase by resolving the test cases in the bugtracker which I created. The test cases are meant to be gone through once before a release to make sure that none of the basic functionality broke because of some obvious bug. How does it work? You just follow the instructions given in the test cases - if norelated (blocking) bug happens on the way, you can resolve the test case.
Get the lastest nightly build/snapshot to test or the latest release package (as installation).
Also, you are urged to also report any other bug you find so that we have the possibility to resolve them before the public release. The release is scheduled as soon as the remaining issues with the update process are resolved.