During 0.6.4 release cycle

Vertigo/Bugs/UnitTestingFrameworkForTheEntireLibrary

Vertigo/Bugs/MakeSureThatLockingActuallyWork

0.6.6

Support for Sender Policy Framework (SPF) or something similar using SMTP AUTH over SSL.

Vertigo/Bugs/SupportForQmailSmtpSending

Automated test-framework, complete test of all services using the actual programs, e.g. testing vertigo-apache requires setting up a server with apache and vertigo running on it, and then doing actual testing. Hopefully this can be done using user-mode-linux.

Vertigo/Bugs/TestFramework

0.6.8

So far the only proposed feature for this release is a vertigo generated/controlled firewall.

Vertigo/Bugs/Firewall

I proposed it myself, but i no longer have a use for it as such (i use an off-the-shelf router now) so i doubt that i will ever get around to doing it.

0.8

This release marks the transition from "static" system to "dynamic" system.

This means that as soon as something changes in the configuration, all relevant servers must be signalled to react to the changes immediately. Services should also be allowed some degree of ability to change the configuration - e.g. when a database service finds that the database option on a domain is not set.

The framework for doing this has yet to be determined, suggestions welcome, so far the following has come up:

• OpenLDAP, proven technology, maybe a bit to large for out uses.
• Spread, seems really great, until you notice the lack for encryption. Hopefully this will change in the future.
• Rolling our own using SOAP or XML-RPC, i'm not too keen on that idea, i would rather use a library where it is already implemented.

This is a "pie in the sky" release, meaning that there is no plans yet on when this will be released, not a single line of code has been written on it yet.