OK, I have updated the roadmap and we have decided on a feature set for the next couple months. This is primarily based upon feedback from talking with customers and where they want us to be. A few things just could not fit into this schedule (TSQL Stored Procs), but will be addressed later.This is a pretty aggressive schedule, but I feel it is very feasible. The key here is consistent releases with functionality increasing. Apr 2, 2007 *New Offerings* Source Code Edition Subscription Service (I will discuss these more in another announcement) Apr 16, 2007 VistaDB 3.0 Build 21 CLR Triggers New samples and how to's Apr 30, 2007 VistaDB 3.0 Build 22 Fixes to reported issues Additional optimizations First release of new documentation (we will be rolling out parts of it from the site before this time, but this will be the first integration with the full setup). May 14, 2007 VistaDB 3.0 Build 23 Full Text SearchThis will be is complete on the 3.0 product and ready for the API changes of 3.1. We have a number of API changes to make for 3.1 mostly to correct the managed datatypes, and correct a lot of the 2.x - 3.x transition headaches. It is just part of my basic philosophy that any changes to a product API must facilate a version number change.  I know a number of people are wanting this very badly, but we just could not make the API changes before adding these other features first. The above schedule brings us to the original 3.0 product matrix quickly, then we can add new things.I know a number of people are wanting this very badly, but we just could not make the API changes before adding these other features first. The above schedule brings us to the original 3.0 product matrix quickly, then we can add new things.