As this thread is starting retroactively in this now long release cycle I’ll first give some context and move to detailing only the most recent releases. The canonical reference for all code changes is in our open source GitHub repo:
This is the ‘rockstor’ package origin. This does not include the Rock-on definition files.
An attempt is made to keep GitHub Release / git tags in line with package release versions but due to a variety of reasons one can lag the other for short periods.
Code Changes so indexed are detailed here:
18.104.22.168 was the first in our current stable channel release (identical to the last testing channel release of 3.9.1-16). It would normally have been earmarked for an iso release but this did not happen. This means we are not well represented currently. Our fault entirely, it’s just a shame, but I suspect our next iso release is not far away and is likely to be based on current stable code (which is looking ripe) and have openSUSE as it’s linux foundation; all prior releases have been CentOS based. See: Rebasing on to openSUSE? and our openSUSE dev notes and status. And will hopefully also kick off a new testing channel release program; hears hoping as we have failed in this regard previously.
We use to use testing channel to develop until we reached a ‘stable point’ and snapshot this as a known good version to be released in the stable channel. This sustainability model was as a result of discussions on this forum: namely the following thread:
This proved to be unsustainable as per our prior arrangement and stable subscribers expressed frustration with being ‘left behind’ / under served in comparison to testing which was only rarely broken anyway. So we changed again, as a value add to our stable subscribers, to releasing Rockstor rpm updates to stable channel only; with the intention of picking up the testing channel again when our resources allowed for this. In open source software it is hard to achieve sustainability and we are attempting to find a way. Our stable channel subscribers are currently that ‘way’.
One of my goals within the project is to return to more frequent iso releases and to resurrect the testing channel but that is going to take time and has failed on us before. But I hold out hope and as we attract more contributors / helpers I see it as a more viable possibility for the future than it was in the past.
Only time will tell.
As per the above intro we can kick off with detailing only the most recent as of writing changes per version in this thread.
Lets skip the first 38 releases for brevity and do a post per version going forward.