The future of Vesta described here is specifically the enhancements that I plan on implementing in Vesta. Development by the Vesta project team stalled around 2008/2009. It doesn't look that any future activity can be expected.
Integration with other development tools
An XML file that enables syntax highlighting of Vesta SDL files has already been developed. An initial version based on the language's keywords is already available. Ass soon as the public repository is running I'll post links to download the XML file and instructions on how to install it.
If needed, plans exist to expand the XML file to understand the Vesta SDL syntax.
Once installed, this XML file will enable syntax highlighting of Vesta DSL in all KDE aware editors like Kate, KWrite, and KDevelop.
Link Vesta with an Issue Tracking software package, like Trac.
Vesta file system update
Vesta exposes its repository files using an NFSV2 interface. As I stated on other pages, using a modern GNU/Linux distribution triggers long timeouts (30 to 60 seconds) when communicating with the server. Adding the nolock option to the NFS mount may eliminate these timeouts, but doesn't address some other problems. Using NFSV2 limits the size of the files that can be stored in Vesta to 2GB.
A couple of paths have presented themselves to correct these, and other problems. One was too update the NFS code in Vesta to support NFSV4. Another was to export the file system as a local file system or a FUSE file system, leaving user who want to use NFS to the distributions native NFS server. Users can opt to use CIFS in place of NFS it they want to. The FUSE based approach is the one I'm taking. File size limitations will be increased to those presented by the file system used to store the repository.
Port the Vesta User Tools to windows. Windows native user tools along with the ability to access the repository via CIFS may make Vesta more desirable to Windows developers. Even with native Vesta tools, targeting Windows will still require the build to be performed on a GNU/Linux host and cross compiling (i.e. mingw).
One of the developers on the original Vesta team is investigating the idea of checking in a Windows VM preconfigured with Microsoft Visual Studio as a stable and isolated build environment. The Vesta runtool would be adapted to spawn the Windows VM and perform the needed build steps. I suspect that any effort down this path will need the updated Vesta file system so the checked in VM image can grow beyond 2GB. There are also many licensing issues that need to be resolved before such a VM can be distributed across multiple machines to perform parallel builds.