The reason we don't have a software roadmap is that we don't want to make promises that can't be kept. Accurately timing software development is rather difficult as I'm sure many people here are aware.

For example, we've spent much longer dealing with bug-fixes in beta5 than we expected. This means that either beta6 will be later than we intended or lack features that we hoped would make it in.

We do have a rough idea of priorities for features but this is constantly changing with customer feedback. Our roadmap consists of "cool stuff will happen" the only variable factor is "when".

--
Mike Crowe
I may not be speaking on behalf of empeg above :-)