SS3 versioning description

The SS3 versioning schema has changed over time, but since the release of 3.30 (which represented a major overhaul of the input and output in SS3 from 3.24), each version has been numbered 3.30.xx.yy, where xx is incremented each with each release of SS3 and yy is incremented with bug fixes and occasionally with a small, isolated change targeted on a specific user application. Any change that forces an input change on all users will be done with an increment to xx. A very major change (such as an overhaul of how SS3 handles areas) would cause an increment to 3.31.xx.yy.

What is a release?

A release provides a significant augmentation to SS3 and sometimes (but not always) a mandatory change in the input file content. A release will also roll up all bug fixes and small changes since the last release. A release is announced via a post to the SS3 vlab forums (by default, members should receive this post, but can sign up for all forum email notifications on the public forum page) and includes release notes detailing changes that have occurred since the last release. The release notes are also posted on the vlab website accessible to the public. Concurrent with the release of SS3, the SS3 GUI (SSI), user manual, helper spreadsheets, and example models are updated and made available on vlab.

What is a fix?

Between releases are fixes. Fixes occur when a bug is fixed or sometimes for the addition of small feature requests (typically from users that need the feature urgently; large and/or non-urgent feature requests are typically documented using releases).

Users can decide if they need to use the latest fix executable by examining the change log in the fixes folder. If there are no changes listed that would affect their model, the user can continue to use the release version. We advise using release versions, unless it is clear that a user is affected by one of the known bugs in a given fix.