CADSWES Maintenance Accomplishment Report Compilation -- August 2017
Phil Weinstein, edit 10-10-2017, initial writing in progress

August 2017 Maintenance Highlights:

1. Ten (10) completed bug fixes.
2. Ongoing: Monitoring and maintaining daily RiverWare regression tests.
3. Ongoing: Installation Process and Licensing development and administration.

Report contributors:

• Substantial content from: David.
• Bug fix items from: Phil (7), Robynn (2), Patrick (1)
• Indicated that they had no maintenance accomplishments to report this month: Mitch.

(II.A) Releases, Patches and Snapshots

There were no RiverWare releases in August 2017.

(II.B) Software Updates, Bug fixes (not associated with new development)

The following eleven bugs were fixed:

1. Bug 5981 (Followup): Plot time axis settings lost saving/loading twice
2. Bug 5987: RPL notes on opt goals are called “Rule Notes”
3. Bug 5989: Object viewer drag object tab cursor can be difficult to see
4. Bug 5990: SCT not refreshing correctly paused RPL Debug, range change
5. Bug 5991: Entering data paused in the RPL Debugger crashes RiverWare
6. Bug 5996: Output Canvas background image not displayed
7. Bug 5997: SCT priority col not correctly sized paused in RPL Debugger
8. Bug 5999: Object Viewer: Switching obj tabs: Loss of treeview expanded
9. Bug 6002: SCT showing only a single flag in legend, load problem.
10. Unfiled: Object Viewer: Minor academic coding error fix.

Additionally, analysis was done on the following bug:

1. Bug 5993: RiverWare crashes whenever browsing for file.

(II.C) Development tool improvements; issue tracking software; modelcomp

(II.D) Enhancements or changes to regression tests (not part of development tasks)

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 the regression tests were monitored and updated as necessary.

(II.E) Download, Install and Release Processes

(II.F) Updates to license software/procedures

(II.G) Updates to download/install/configure user documentationt.

(II.H) Modification to Web pages for downloads and installs

None reported for August 2017.

--- (end) ---