WaveMaker 6.4.5 GA is now available. This is an incremental improvement (over 6.4.4) and includes LiveForm improvements, performance improvements, and bug fixes. For details see the WaveMaker 6.4.5 Release Notes.
If you read yesterday’s post and are wondering about release nomenclature … WaveMaker 6.4.x continues with the old numbering and naming scheme. WaveMaker 6.5.x will following the number and naming scheme described yesterday. More information on WaveMaker 6.5 will be available from this blog and on dev.wavemaker.com shortly.
We are closing in on the first drop of WaveMaker 6.5 so I thought I’d provide information about some of the infrastructural changes we’re making in WM 6.5. Some of you may have noticed that our source code is now on GitHub. GitHub contains the absolute, up-to-the-minute development code. If you are are quite brave and extremely impatient you can download the latest code and build your own version of the latest efforts of the WaveMaker development team. For most people I recommend waiting for the official drops rather than building your own version.
We’ve also upgraded the WaveMaker build process to use Maven and will update our release nomenclature to follow standard conventions. The new nomenclature for releases will consist of milestones (designated by ‘M’ followed by a number), release candidates (designated by “RC” followed by a number), and releases (designated by “RELEASE”). For those of you who are accustomed to the previous WaveMaker nomenclature, here’s the translation:
|Old Designation||New Designation|
where ‘#’ is incremented for each milestone (M) or release candidate (RC).
The first drop of 6.5 will be named “WaveMaker 6.5.0 M1″ (in the previous scheme you’d have expected “WaveMaker 6.5.0 DevBuild) and the next milestone will be named “WaveMaker 6.5.0 M2″ (rather than “WaveMaker 6.5.1 DevBuild”). This approach follows conventions used commonly within the industry and by SpringSource.
We are targeting to deliver the first milestone (M1) in the next few weeks. Stay tuned to this blog for more info.