Rockstor’s 3.9.1-16 testing channel release (last version of our CentOS based testing channel before it became deprecated) was released around November 2017:
Making it just over 2 years old.
See the following forum thread for the background to this channels deprecation:
And our docs section Update Channels has some more info on our update channels and the pending revival of our developer orientated testing channel releases.
Last stable channel release, noted in the above forum thread was 5 days ago.
OK, so Rockstor is a GPL v2 and later open source project that does accept pull requests and is attempting to fund it’s own sustainability purely in the software realm. This is a common and non trivial problem that has few example solutions. Our current Stable channel subscription is an attempt at this sustainability.
If you would like to address some of these ‘strange’ shortfall for the time we have been in development you are more than welcome. In which case you may find the following Community Contributions docs section and specifically the sub section of Developers of use. But if you do fancy diving in and offering some improvements note that we are well under way in our move to re-basing on a “Built on openSUSE” variant by way of a ‘re-launch’ of sorts. So in which case it is expected that any code contributions are also tested on openSUSE Leap15.1 and Tumbleweed. This has been a fairly massive, but necessary, burden on our limited development resources. But in the end will ensure that our users have an enterprise grade linux that has upstream btrfs support, along with boot to snapshot capability and a community lead upstream.
Yes an rsync service would be nice, but in the midst of our ‘transition’ is unlikely to be added by any of the core developers currently. But if offered up by way of a pull request it is likely to be very welcome. I’d like such a facility myself. But if this is a requirement you can always go the command line route for now; for this you would have to look to CentOS 7 instructions on setting this up. And if the target was an existing Rockstor share (btrfs subvol) then you would at least have the Web-UI facilities on this share.