I want to download rockstor, on the Download page it seems like the latest stable version is 4.6.1-0, but there’s nowhere to actually download that on the page? So maybe the latest testing version, which according to the download page is 5.0.13, but the forum/github says 5.0.14, but the download links all go to 5.0.9. Am I misunderstanding something simple here or are the downloads just really confusing 
@nixcamic Welcome to the Rockstor Community forum.
Agreed this is confusing, but there is a ryme to our reasoning here.
From the top-of-page table that is correct.
From the first 2 lines on the downloads page:
Installers include first Stable or RC* status ‘rockstor’ packages.
Rockstor 5.0.9-0 = Stable Release Candidate (RC4)
We instead offer the far newer (by years in some of our dependencies) Stable Release Candidate.
The reasoning here was to get folks started on the far newer versions we had in testing as they were already at Stable Release Candidate status; i.e. almost at stable. This way new installs don’t start out so far back in our history. Ergo get folks on what is nearly stable so they can, in turn, help with the polish ready for our next stable. We traditionally have installers built around RC or first stable version rpms. But given the length (time taken) and the extensive developments in this current phase we ended up re-rolling our installers a little earlier than usual. Otherwise folks would still be installing our prior Leap 15.4 (last stable rpm) where-as RC (from current testing ) was required to be compatible with Leap 15.6 (current preferred base). So we are simply trying to offer folks the newest practical offering we have (RC4) at time of last installer build. This also helps with weeding out installer related issues.
As from last week, our downloads table needs updating:
As that is the last installer we build. We will be re-building the available installers likely once we have our first Stable rpm identified.
No; you likely see what is there, and yes this is a challenging transitional stage.
Our dependencies had become unreasonably old (in master/stable channel), hence the more reasonably updated RC rpms, built from our testing branch, made available in the installers to get folks off to a way more modern start. We had tones of feedback in this latest testing phase, as can be seen in its entire history from the following two links (3rd line of Downloads page).
Stable Release Candidate status — GitHub Milestone
So in short we felt it best to get new installs out-the-gate on testing RC as it was compatible with newer Leap, and last stable was not. Plus we do not yet have a first Stable rated rpm: but we are very close now.
Hopefully that answers your questions, and alleviates some of the confusion.
2 Likes
The referenced issue is now resolved.
2 Likes