Skip to content

NovaStar Core / Release Notes

This appendix provides information about changes that have occurred in NovaStar core software. A summary table is provided, with links to details for major versions.

NovaStar Core Version History

The following table summarizes the NovaStar core system release history. Links are provided to detail pages. Only recent versions are documented in detail. Comments for minor versions may be listed under a version that is publicly released, rather than the development release when a feature was initially added.

NovaStar Core Version History Summary (most recent at top)

Version(s)                     Summary of Major Changes in Version Release Date
5.4.0.0 Feature release to add support for Debian Bullseye. 2023-07-14
5.3.2.0 Feature release to improve data polling and import programs. 2022-09-16
5.3.1.3 Maintenance release to fix issue with nsrecdata custom specification binary encoding. 2022-04-20
5.3.1.2 Maintenance release to fix issue with nsrecdata custom specification binary encoding. 2022-04-18
5.3.1.1 Maintenance release to fix issue with nsrecdata custom specification binary encoding. 2022-04-15
5.3.1.0 Feature release to implement nsrecdata custom specification binary encoding, add nscore and nssecurity programs. 2022-04-05
5.3.0.2 Maintenance release to add sub-second logging to nsrecdata. 2022-03-15
5.3.0.1 Maintenance release to fix nsrecdata issues. 2022-03-01
5.3.0.0 Initial Debian Buster operating system update. Significant core system cleanup to improve command line program consistency and support automated testing and troubleshooting. Improve data collection software. 2022-02-24
5.2.1.1 Maintenance release to fix statreport monthly report. 2021-11-11
5.2.1.0 Feature release to add support for Kore Wireless Iridium data service using ALERT2. 2021-03-04
5.2.0.1 Maintenance release. 2021-06-08
5.2.0.0 Debian Stretch release with improvements to installer. 2019-11-20
5.1.4.8 Maintenance release using improved software build system. Integrate submissions from HydroLynx. 2019-10-07
5.1.4.7 and earlier Older releases including from HydroLynx.

NovaStar Core Version Numbering Convention

NovaStar core software versioning adheres to the following pattern, which is generally consistent with Semantic Versioning. The version adheres to the following convention.

Generation.Major.Minor.Patch[.Modifier]

where:

  • Generation - number indicating NovaStar product generation
  • Major - number indicating a major change to the software, expected to occur infrequently (e.g., for operating system or database design changes)
  • Minor - number indicating a minor change to the software, expected to occur as features are added (e.g., new software features)
  • Patch - number indicating a patch release, for example to fix a bug, expected to occur between feature releases, as necessary
  • Modifier - The version may also be followed by a modifier such as .dev1 to indicate a release that is under development

The above version string is used in the software as follows:

  • the version is used in software installer filenames
  • the nsversion program will output the version
  • the version is also used for individual core system programs and output with -v, -version, and --version command parameters

Separate software components such as Data Web Services and Operator have their own version number.

Release Notes Issue Icons

The following icons are used to indicate the type of issue in release notes.

  • limitation Known Limitation – A known limitation has been documented and may impact the user. The limitation will be addressed in a future release unless there are significant technical challenges.
  • bug Bug Fix – A bug has been fixed. Users should evaluate whether their work is impacted. Sometimes bug fixes impact internal code and changes may not be visible or obvious to users.
  • remove Remove – A feature has been removed, generally because functionality has been migrated to other code or the functionality is no longer needed (e.g., a web service response data field is no longer available).
  • change Update/Change – An existing feature has been changed or enhanced. Backward compatibility is usually retained. Modifications to an existing service are considered to be a change.
  • new New Feature – A new feature has been added, such as a new service. New features may or may not be obvious to users but will generally be visible in documentation.

Known Limitations

TriLynx Systems tracks issues in the development system and coordinates development and maintenance with clients.