Tim,

I have just checked the updated roadmap. Is everything you working on  published there? I was hoping to find replication filtering and linux
support, but not even on the list.

I am also waiting for raw support and the improved query optimizer. These are musts for me to step forward with EDB from the test phase. If I
got it right most of the bigger changes in the roadmap are depending on raw support, still  I am a little bit worried  that packaging all planned
2.04 functionality might result many months of waiting.  

So here is a  suggestion inspired by the way cached updates were introduced. Could it be that instead of releasing a couple of new functionality
at once,  you could share what ever is ready and does not have possibly problematic dependencies with ongoing developments? You could
make a list of changes intended for the next version  but the version number is  increased only whenever the last item is done.  

Leslie     

Leslie,

<< I have just checked the updated roadmap. Is everything you working on
published there? I was hoping to find replication filtering and linux
support, but not even on the list. >>

I'm updating this as I go, so that list will always be in a state of flux.

<< I am also waiting for raw support and the improved query optimizer. These
are musts for me to step forward with EDB from the test phase. If I got it
right most of the bigger changes in the roadmap are depending on raw
support, still  I am a little bit worried that packaging all planned 2.04
functionality might result many months of waiting. >>

I assume that you mean "row support" ?  If so, then no, you won't have to
wait months for it.  It's the only thing that didn't make it into 2.03 that
was close.

<< So here is a  suggestion inspired by the way cached updates were
introduced. Could it be that instead of releasing a couple of new
functionality at once,  you could share what ever is ready and does not have
possibly problematic dependencies with ongoing developments? You could make
a list of changes intended for the next version  but the version number is
increased only whenever the last item is done. >>

That's what I intend to do, since it is exactly what I did with 2.03.  Much
of 2.03 was in the product prior to the 2.03 release.

--
Tim Young
Elevate Software
www.elevatesoft.com