v3.0-1

Changes:

• All messages now go to STDERR, except for the output of ssu re <upgrade_version> and version dup (which still goes to STDOUT) or when help is called.
  Nevertheless all output messages after confirming to upgrade are still recorded in a log file.
• Implemented an own, more robust function to perform SailfishOS version string comparisons.
  This is also rectifying the usability issue #24.
• Enhanced fail safety a bit more.
• Much more elaborate downgrade checks and messages, now unconditionally inhibiting a downgrade "across" a "stop release".

v2.9-1

Changes:

• Add rpm to the list of processes to be terminated
• Fix issue #23 (thanks to @FrankUllmann for reporting and analysis)

v2.8-1

Change:
Also terminate pkcon, zypper (processes) and stop osupdate-check.service (user) right before upgrading

v2.7-1

Changes:

• Stop AlienDalvik's services in the reverse order they are started (as it is already the case for all other service groups)
• Also stop OSM Scout Server's services
• Add a facility to terminate running processes
• Terminate Store-client, Storeman, Warehouse, OSM Scout Server and / or OSMscout, if running

v2.6-1

Change:
Add AlienDalvik to the list of system services to be stopped right before upgrading; as AlienDalvik may start any (number and function) background task automatically, which may use significant CPU-, RAM- or I/O- (LAN, eMMC etc.) resources at arbitrary times, it is in some sense "worse" than the systemd services, which are already stopped by sfos-upgrade 2.5.
That implies that now all Android apps are automatically stopped when starting the upgrade proper, but that should be (manually) ensured, anyway; thus stopping AlienDalvik ultimately just guarantees that.

v2.5-1

Changes:

• Detect failure to retrieve version numbers of all public SailfishOS releases
• Also check for omitting a "stop release", when called without a parameter
• Tried to unify message structure: The first line of each output statement of the sfos-upgrade and post_sfos-upgrade proper is now prefixed with an "Aborting", "Warning" or "Notice", plus each "Warning" and "Notice" ends with an empty line (which is superfluous when aborting), emitted when the specific check or balance is finalised.

v2.4-1

Changes:

• Improved speed and coding style of the facility, which stops arbitrary systemd services
• Unified wording of user output in the part, which logs to the logfile (i.e., throughout the last third of the sfos-upgrade script)
• Hopefully caught the last spots of inconsistent and bad coding style

v2.3-1

Changes:

• Enhanced facility, which stops arbitrary systemd services, to support stopping user services in addition to stopping system services
• Minor coding style improvements

v2.2-1

Changes:

• Created a facility to stop arbitrary systemd services from the code, which stops cron.service
• Enhanced the facility, which disables all Openrepos' repositories, when upgrading from a SailfishOS version below 1.0.4.0

v2.1-2

Changes:

• Coding style improvements
• Calling bash in the sfos-upgrade script
  Still all three script's code is maintained as fully sh (Bourne Shell) compatible.
• Killing store-client softly, but for sure (in post_sfos-upgrade)
• Fixed a cut&paste error, preventing v2.0 and v2.1-1 from upgrading SailfishOS versions below 1.0.4.0
  Many thanks to @Self-Perfection for testing v2.0-1, spotting the error, plus creating pull request #19.