Hi Dan,
Our original plans were to release 6.4.0 Release d quite some time ago, but as always, depending on the results of our QA and beta testing. All changes made to the framework have the potential of being destabilizing, and the more enhanced features added, the more risk for destabilization.
For most of Visual WebGui users, releasing an unstable version has little or no value, so while we still get new QA/Beta reports for problems that were working on the last released version(s) or for some reason must be fixed in relation to others already open on 6.4.0 Release d, we face a bad dilemma.
For some Visual WebGui users there is more value in having an unstable release to be able to develop against new features in the upcoming release, than to be "stuck" at the old released version. In addition, having access to that unstable release gives the user the chance to verify if his problems have been solved or not. For those users we have suggested that they email a request to support for joining the beta testers team, which will grant them access to those unstable QA releases for this purpose, knowing the QA versions are not stable enough to release.
I know this sounds like I'm trying to avoid naming any date we will commit to, and that's partly correct, as at this point I simply do not have this information, although I have tried squeezing it out.
You can at any time see the status of our upcoming release here and look at the Versions column for 6.4.0 Release d, which at this point has 66 unresolved entries. It's not guaranteed that all of them will indeed be fixed in Release d, as some of them may need extensive changes that my have to wait for a later version.
I'm sorry that I can't be more specific, but hope this explains our situation a bit,
Palli