@Jorma_Tuomainen Hello again.
We are about to release Stable Release Candidate 10 (RC10) by way of 5.0.15-0 in testing. See:
For the anouncement when it arrives. And for our current testing channel progress towards the next Stable rpm.
Latest testing rpm is available for all the current Leaps and TW. See our more recent table at the top of the downloads page re what rpm is available for what Leap:
Plus one can always apply all non ‘rockstor’ package, i.e. all upstream OS updates, irrespective of testing/stable channel selection as per the instructions here:
https://rockstor.com/docs/installation/install.html#updating-rockstor
And we now have a full complement of OS distribution update how-tos:
- Distribution update from 15.2 to 15.3 — Rockstor documentation
- Distribution update from 15.3 to 15.4 — Rockstor documentation
- Distribution update from 15.4 to 15.5 — Rockstor documentation
- Distribution update from 15.5 to 15.6 — Rockstor documentation
So if you are on the now EOL Leap 15.4 for example we do have, as per the referenced downloads table, our last Stable ‘rockstor’ rpm also published for Leap 15.5 which is not yet EOL. But given we are in late RC releases in current testing channel, you could also choose to jump to say 5.0.14-0 to get RC9. But I am currently working on getting RC10 out the door.
For further context, the current testing phase was a real challenge as we had to update every element of our back-end. This was non-trivial give the age of Django and our prior use of Python 2.7 etc in the last Stable rpm. So we faced, and have now almost faced-down, the famously rough migration off from Py2.7 to Python 3.*. But again, all other OS updates are available as per a regular openSUSE install, given our “Built on openSUSE” grounding.
Once we have 5.0.15-0 (RC10) out, I’m also hoping to do an across the board rebuild of all downloadable installers also. Given we have made some significant progress on from our current installers that were released with RC4 (5.0.9-0) - to help folks along out-of-the-box as it were: given the really long and as mentioned challenging testing phase that we are now nearing the end of.
Hope that helps. At least with some context and options.