re: RT versions… this is way too much info, but it explains how I keep track of all the s/w releases from Aillio. I use Win 10 so I can’t help with the other s/w packages, but in Windows-
- On GitHub, I pay attention to “commits”; if the number of commits increments upward, I download the release to a location where I keep all the Aillio RT files. I edit the file name to give it a unique temporary identity without losing the basic ID usually by inserting “.xxx” after the basic file ID.
- Right-click the file name and click Properties.
- Choose the Details tab and note the Production Release number. I use this info in my naming convention for the file just downloaded. From what I think I understand,
– if the Production Release ID is new (increased), there is possibly a change to the s/w that affects behavior;
– if the Production Release is the same, there is probably no change that a user will recognize.
When RT is being worked on there can be a lot of changes. I worked out a way to keep track of changes to RT by modifying the file name slightly to add the Production Release number and the number of Commits. For example…
- the first release of RT for the current ‘-stable’ release was on 2 Dec 2019 and was named “RoasTime.Setup.2.5.5-stable.exe”. To keep track of this release I created a unique ID of “RoasTime.Setup.184.108.40.206-stable(05).exe” and installed the new version.
– “.226” refers to the Production Release number and
– “(05)” refers to the number of commits.
- a few days later on 6 Dec 2019 the number of “commits” changed to "8"and I d/l’ed the new file;
- Properties -> Details -> Production Release showed a change, so I saved the file as “RoasTime.Setup.220.127.116.11-stable(08)” where “.227” is the new Production Release and (08) is the new number of “commits”.
- Since 6 Dec there have been 5 additional changes to this same root-ID of RT (4 Jan, 6 Jan, 9 Jan, 14 Jan & 16 Jan). That’s seven releases in all to RT 2.5.5-stable though I think only the second had changes that may have affected behavior. I saved them all with a unique file name for each that includes the Production Release number (unchanged for the last 5) and the number of commits (each is different). I also installed each to be sure they didn’t crash (they don’t).
I also keep track of (and d/l) -alpha, -beta and -internal releases but none of these have changed since Dec 2019. My preference is the -beta release, but the current -alpha, -beta and -internal have a problem when viewing older charts that causes the displayed temperatures to switch from °F to °C after the first chart even though the chart labeling says °F. Since I keep an archive of all the d/l’s I can revert back to something that works if I have to… which is how I happen to be using the current -stable release.
As I said, way too much info (mea culpa!). But we have a development environment and sometimes a release will have issues so I have to be able to back-track to keep roasting. In truth this is a level of detail fussiness I avoid, but I swore I wouldn’t get caught again when I crashed hard back in Sep 2019.