We'll do 3.0.25

[Alan DeKok]

  It looks like there's a last-minute bug introduced in 3.0.24 which breaks the server.  Sorry.  :(   It passed all of the regression tests, so we'll need to update the tests.

  Matthew will be releasing 3.0.25 shortly to fix the issue.

  A major issue with current development is that v4 is taking longer than we'd like.  The end goal is in sight, but there's still a lot of work to do.  We believe the result will be worth it, and surprisingly simple / powerful / useful.

  But in the mean time, we do need to get new functionality into v3.  So after some internal discussion, our way forward is this:

* Matthew will release 3.0.25 shortly

* after that, the v3.0.x branch will be frozen for everything other than security fixes

* we will create a v3.2.0 branch which will contain all new development for v3

* 3.2.0 will be 99.99% compatible with 3.0, so any upgrade will be painless.  The same configuration files can be used

  The goal is to have a clear distinction between "stable" 3.0, and "new feature" 3.2.

  Sorry again for the issues.

  Alan DeKok.