Release Notes: This release fixes a bug in upgrading MySQL schema (apologies to MySQL users).
Release Notes: Increased variable name size. Dots accepted in variable names. Bugfixes (offline deployment actions not executed; could not upload an overlay at the root level of a package; pre-setup script not executed unless a post-setup script was defined; and some kwatee variables had incorrect values after a deployment freeze.)
Release Notes: This release no longer performs automatic integrity checks before stopping operation. It fixes "environment variable server/package qualifiers lost in import" and "environment bundle import fails in 'upload' mode"
Release Notes: A major issue with zip archives which could not be uploaded is resolved. A cosmetic issue with overlays showing at the root of archives is resolved. kwateelib (and therefore update.py) can now update archives even when kwatee is not running on localhost. Be sure to use the latest kwateelib task in your deployment automation.
Release Notes: This release fixes an archive update failure via ant/maven when the kwatee URL was not on localhost.
Release Notes: This release adds support for regions in EC2 server pools. It fixes an occasional maven task "bad parameter" error and a serious bug that caused all logins to fail after an attempt with an unknown user was made.
Release Notes: A long file name issue in the agent was fixed, and result codes in the RESTful API were improved.
Release Notes: This release fixes a port=0 issue with manual server pools and adds support for long filenames in tar archives. Kwatee can run with Jetty server as an alternative to tomcat.
Release Notes: This release cleans up the REST interface and related Python/Ant/Maven support, and adds support for create/delete version and freeze/delete deployment (see the documentation). "Internal Error" messages are now replaced by more explicit descriptions.
Release Notes: Files above a certain size incorrectly generated a check integrity error (note that existing archives must be re-imported). Browse/Customize archive caused an internal error in some conditions. Deployment write errors (i.e. no more space) caused files to be partially deployed without reporting errors. Full deployments sometimes silently failed. These issues have all been fixed.