SPADS versions and releases

[Jools]

I have some autohosts that are using the testing version, they are currently at spads version 0.11.37. Then I also have some versions that use the unstable, they are at 0.11.38a. I wonder, again if it's been asked before, what's the difference really, and if one can just change to the unstable by editing the configs?

[bibim]

• SPADS stable/testing/unstable releases are based on Debian's release scheme. Basically for SPADS it works this way:
  
  The unstable release is the release containing latest developments: every time I change something in SPADS code, I perform unitary tests first and then, just after, I update the unstable release with these changes. Basically I use the unstable release for integration tests, so this release is not recommended for normal use.
  
  When I consider the changes of the unstable release are unlikely to contain severe bugs, I apply them to the testing release. This usually happens after 1 day or a few weeks, depending on the changes and my free time. The testing release is the recommended release for SPADS because it is a good compromise between stability and new functionalities.
  
  The stable release is updated much less often. Basically it's only updated once the testing release hasn't changed for a long time and no bug is identified.
• SPADS version numbers are built like this: 0.<majorVersion>.<minorVersion>
  
  When two SPADS versions have the same <majorVersion> part, it means there is no breaking change in SPADS configuration files format, so you can use one version or the other without modifying anything in your config files.
  
  In your case ("0.11.37" vs "0.11.38a"), SPADS major version is the same ("11"). It means you can update your 0.11.37 autohosts to 0.11.38a just by changing the release in spads.conf from testing to unstable. No other manual action is required because configuration files are compatible between these two versions.
  
  But anyway, there is absolutely no risk to break a SPADS installation just by changing the release in spads.conf, because if SPADS detects that the new release has a different majorVersion number, it will run normally without auto-updating. Instead, it will print a message telling you what manual actions you have to perform if you want to update. Then you can choose to follow these instructions or reverse to the original release in spads.conf to keep current version. So it is totally safe to "try" several releases at any time just by editing spads.conf

[Jools]

Thanks, very well written and informative. Just what I wanted to know.