@CJ_and_Darren Hello again.
Thanks for the offer. It’s actually getting close to the time when it would be appropriate for more general testing, but currently it’s still pretty much in the developer only stage as what we really need is direct assistance with the fixes themselves. It’s still a target rich environment . Once we have the most obvious stuff done then I or @Flox will annouce this and that way we can get on with the final refinement via wider testing with the aim of achieving feature parity with our CentOS variant and then finally releasing the ‘Built on openSUSE’ Stable channel rpms. Can’t wait myself personally, but all in good time.
I’d say wait until at least 3.9.2-54 (next release) as there after we expect samba and email notification to actually work. From there on it should be down hill. Thanks to forum members @Flox, @def_monk, @gaspode, @Marenz, @luke, @Psykar, and @tyukh for their efforts with ongoing recent bug squashes on the openSUSE side.
But by all means do take another look at our companion post re the now released ‘Built on openSUSE’ testing channel. I’ll update this thread soon on the missing 10 months of progress since my last post here. But our 3.9.2-* Stable channel announcements have served this purpose by flagging all openSUSE releated issues fixed in the interim.
Thanks again for the offer and maybe there is some utility in just getting Leap15.1 on that rather fancy HP server you have ready for the pending rpm updates. Plus we are now down to just a few tweaks from default Leap15.1 install, prior to testing repo add, so I say give it a go but there are just not enough core developers to assist with this process without in turn holding up the larger mission. Hence the request for developers. But if you are game I think 3.9.2-54 may be worth a look. Oh and the current 3.9.2-53 should be able to update in place, via the Rockstor Web-UI to -54 when it comes out. Just in case you are really eager. But remember this is not a supported release, we need the support of others actually, hence the linked post stressing developers. But I think you get the idea.
Great to have the early adopters on board with this, it can only help. But again folks, please appreciate we are a pretty small team, so ideally, as the linked post states, we are mainly in need of the actual fixes, rather than the reports of sub system failures as they are, at this stage at least, fairly easy to identify.