Just a quick update on 13.3-BETA.1 testing. It’s been out a couple days now and we’re eager to see more community folks give it a whirl and report any issues. We’re keeping an eye on the numbers and as of right now the overall count of testers is low. Compared to Dragonfish, we are seeing less than <4% of the testers over the same period.
That said, we are asking for an assist from any of our community CORE users. We’ll keep an eye on it over the next few weeks. If we don’t see enough testing systems right away we may push back the RC1 timetable to give a bit more time to shake out any lingering issues. We’d like the eventual launch of the .0 to be of the highest quality possible, and the more testing we have will help us all towards that goal.
Getting feedback is critical to delivering quality. Since 13.0-U6.1 is the most popular version ever, we will be reluctant to release without a large number of testers. We will delay RC.1 and RELEASE to get that testing and quality assurance.
If you do test 13.3 BETA, please either report bugs or respond here with your experiences. If the experience is positive, that will encourage more users to test and accelerate the process.
I wonder why all the SCALE RC / BETA / release versions show up though and not the CORE BETA. That’s kind of inconsistent.
It’s also odd that TN CORE is not labeled as such in the menu…
@Kris and @Captain_Morgan, I suggest you add a link to the manual update file in this call for beta testers. The more barriers you put up to BETA testers, the fewer will help out.
It’s solved and the fix committed. I (and everybody else depending on replication) just need some instructions to patch my NAS manually so I can continue to run and test the BETA.
I’ll possibly just dig in the commit later today and try to apply the changes - with vi(1) if necessary.
@kris I also deleted the debug files from the issue in JIRA - so I guess it could be made public again.
Shell isn’t missing - it was removed since the consensus was that iXSystems shouldn’t ship something that buggy and iXSystems also doesn’t have the resources to fix it.
Thank for trying one system… finding bugs in BETA versions is precisely the goal. In this case, replication on netcat to older versions.
As a general rule, we’re not recommending production systems on BETA. Spin up a VM, use some spare hardware or try it on a non-critical system. Diversity is useful at this stage.
If you do find a bug, try the Nightly version after it is fixed.
Updated 2 systems (old AMD & newer i3) to beta yesterday (very simple - just smb guest access). Reporting was broken on i3 but gui offered “fix” which worked. Not replicable. Still miss loss of the shell within the gui. Otherwise, no issues identified.
John
)
