CADSWES Maintenance Accomplishments -- August 2013 (edit 9-9-2013)
RIVERWARE
RELEASES, SOFTWARE MAINTENANCE and DEVELOPMENT ENVIRONMENT
Releases and Patches
Preparation for the version 6.3.3 patch release (released on 9-3-2013).
RIVERWARE
RELEASES, SOFTWARE MAINTENANCE and DEVELOPMENT ENVIRONMENT
Regression Tests
The regression tests continue to be maintained on a daily basis. This involves updating the regression tests to exercise new developments in the code. Also, as new code is added to the development area, the model comparisons performed in the nightly regression tests usually show differences (for example, because a new method category may have been added). When this occurs, the regression tests need to be updated to reflect the current state of the development area so model comparisons do not fail. In addition, every week, the daily history of each regression test is analyzed to determine if the run time or model size has significantly changed because of new development. In August, all the tests were updated when the Local Inflow method names were modified for spacing and capitalization.
RIVERWARE
RELEASES, SOFTWARE MAINTENANCE and DEVELOPMENT ENVIRONMENT
Development Snapshots
Two version 6.4 development snapshot releases were generated in August 2013.
RIVERWARE
RELEASES, SOFTWARE MAINTENANCE and DEVELOPMENT ENVIRONMENT
Download, Installation and Release Process
RIVERWARE
RELEASES, SOFTWARE MAINTENANCE and DEVELOPMENT ENVIRONMENT
Licensing
Generated and delivered (or in the process of issuing) license files to RiverWare users. Tasks included tracking the expiring licenses, contacting users to get information; generating license files; updating the license data records; providing instructions for RiverWare download, install, and floating license server manager configuration setup; and problem solving for users.
RIVERWARE
RELEASES, SOFTWARE MAINTENANCE and DEVELOPMENT ENVIRONMENT
Software Maintenance - Qt4 Port
During testing of the Qt4 port of ClientServer, it was found that if a server was started and then the model was reloaded, the server would shut down as expected with clearWorkspace(). However if data was then attempted to be transferred via that same type of server, the ServerProcTable would have an active listing for the server that it would attempt to connect to, even though the server was gone. This would generate a DMI error. The bug was in some ported code where a string comparison of the server name was no longer succeeding when the server should have been removed from the ServerProcTable. Fixing this comparison code restored the original behavior to allow removal of the server from the table.
--- (end) ---