Blaise NG Progress

We are working very hard to get a Community Technology Preview (CTP) release of Blaise NG ready before the end of the year.
The status of the various project parts is as follows:
Control Centre
We have rewritten a substantial part of the control centre, because some of our users didn't think it was a good idea to store Blaise source files in a database. Furthermore, we have changed the way the control centre handles projects.
Language
Most language constructs are now supported in Blaise NG. There are some special cases, like alien routers, that haven't been implemented yet. The XML2BMI tool, which converts Blaise NG meta files into Blaise 4.8 meta files, is in the testing phase.
Syntax Editor
For the CTP release, we are not going to change very much in the syntax editor. It already supports syntax highlighting, code snippets, intellisense, and code completion.
Datamodel Designer
The datamodel designer, with which you can graphically design a questionnaire, is not ready by far. It has proven to be much more difficult than we had expected. For now, we have to decided to leave it out of the CTP release.
Layout Designer
We still have a lot of work to do on this part of the project. We have made a rudimentary version of a template designer (the WYSIWYG equivalent of the modelib editor). We have hired an external designer to help us create nice-looking templates.
Meta Viewer
The meta viewer is ready.
Runtime
We have a working version of the Data Entry Service ready. It is possible to fill out a questionnaire both online (using a silverlight-enabled browser) and offline (using our WPF data entry program). The rules are executed by the Blaise 4.8 API service, and the data is stored in a Blaise database.
Data Viewer
We have a simple version of the Data Viewer ready. It does what it's supposed to do: show data.
Documentation
Documentation is complete. Well, almost. Okay okay, we still have to write the documentation. But we have started a documentation project, and we have selected a tool with which we can create a CHM help file, a web site of the help file and a PDF-version of the help file, which can be used to print a book. We are currently looking at the Blaise 4.8 help file to see which parts we can reuse in Blaise NG.
Installation
We have licensed InstallShield 2010 as our tool for creating our installation. The .NET framework 3.5 (SP1) and Silverlight are required to run Blaise NG, so we install them before starting the Blaise NG installation.
Conversion
We still have to write an import tool, with which you can convert your Blaise 4.x datamodels to Blaise NG.

As we are nearing the CTP release, we need to have a testing strategy. We have decided to hire an external tester, who is going to create a test plan and help us set up an automated testing facility.