The DevBuild for WaveMaker 6.0 will be available in the next few days. We’re excited to offer the DevBuild to all registered members of the WaveMaker community and look forward to hearing your feedback, suggestions, requests and even bug reports.
WaveMaker 5.2 delivered some important new capabilities but we felt we needed to improve upon the release process used in 5.2. The DevBuild cycle was too short and limited the community’s ability to provide input. In WaveMaker 6.0 we will deliver a DevBuild followed by a Beta and then, finally, a GA. The release process will be longer and we expect a better release as a result.
During the DevBuild we’d like the community to actively participate in the feedback process. Please continue to use the forums to expose any issues you have with the release: bugs, improvements, feature ideas, even small annoyances. From the forum posts Jira issues will be create by WaveMaker staff and designated community members. The WaveMaker Engineering team will actively monitor the forums and Jira and will strive to resolve as many issues as possible. Of course, project test cases are always appreciated as they often accelerate our ability to reproduce and resolve issues. As part of the WaveMaker 6.0 release process, additional releases will be available: DevBuilds and/or Betas, so you’ll be able to monitor and validate our progress.
You’re probably wondering, what’s in WaveMaker 6.0? The answer includes: widgets, multiple hibernate sessions, improved internationalization, multitenant support, and bug fixes, bug fixes, and more bug fixes. WaveMaker 5.2 delivered a number of Dojo widgets, including Grid, Chart, and Menu. In WaveMaker 6.0 you can fully configure and control these widgets from within Studio to more easily utilize their capabilities. We’ve extended the database system to enable multiple Hibernate sessions initiated from within a Java service. WaveMaker 6.0 simplifies internationalization. In addition, for Enterprise customers WaveMaker 6.0 delivers automated multi-tenant support. With a simple configuration change WaveMaker will automatically isolate database accesses between the customers (tenants) of a software as a service (SaaS) solution.
Are you wondering whether that one bug that really annoys you is fixed? There’s a good chance it is. We’ve worked to correct many of the issues reported by the WaveMaker user community. At the time of this blog post, we have fixed 59 bugs and delivered 25 improvements and features (see Jira for details). And we’re not done. We’ll be fixing many more during the DevBuild period so now’s the time to provide your input.
I fully expect this will be the best WaveMaker release ever. We’re looking for your help to ensure the release meets our expectations and, more importantly, yours.
I’ll post again when the DevBuild is available. It’s a just a few days away.