While I was not impacted by the update, I noticed that the release notes did not announce the correct build number and posted about that. This was later corrected, but in these circumstances it would be nice if there were any feedback on the thread opened to make the error known, and to those who advised Roon staff via direct message.
In addition to that, you should really make sure the release notes are written in clear and unambiguous terms. It was in no way clear from what was written on the B1324 notes, that this was the ‘first exercise’ of the new staged-release system. The notes stated that
In the future, be sure to check our release notes if the latest update is not available to you. When an update is being released with a “staged” rollout, the release notes will notify Roon users and will provide additional details about when everyone can expect to get the latest changes.
Nor did the release clearly state that this was a (first) staged rollout, nor were there any additional details about when we all could expect the latest changes. The release notes were ill-written, and this added to the confusion during the weekend.
May I ask why so important feedback, even for a ‘few’ users , (almost) never is posted at the top of the forum but in a singular user topic, which will dissappear from the screen in a few hours (at most)
I recommend manually installing the latest version from our website on any Roon install on Windows that is failing to start after taking the update. If you are not having that symptom on one of your installs, there is nothing to for you to do on that one.
There is a limitation in the Discourse forum code that is probably related: Posts can be pinned to the top, but they are automatically unpinned for each user who reads it. Their intent is “you should read this once”.
And as I noted before during the weekend in this thread, Roon forgot to update this summary post for the B1324 update as well and it still shows 1311, which should be fixed as well, because it does say:
Of course, it would be very helpful to have this at the top of Software Release Notes at all times because sometimes the build numbers get out of sync between the different platform. The problem is, this post was created in September 2022 and as soon as you read it, it gets automatically unpinned and falls far down, unless you remember to re-pin it again for yourself. Which is probably why Roon forgot to update it in the first place.
This temporary pinning behavior was discussed in the Discourse forum and Discourse forum admins asked to have a setting that allows such pinned posts to be instead permanently sticky at the top of certain categories (and to have this a per-category setting, so that too many sticky posts don’t pollute every category). This was refused by Discourse but they pointed out that an option already exists to configure this for a whole forum. I.e., if Roon chooses, they could make pinned post permanently sticky at the top everywhere.
It seems to me that Roon doesn’t use pinned posts excessively, so maybe @brian could consider if this is an option.
The discussion and the reference to the existing setting is here:
Rather than reinstall the applications on both servers (windows 10) I went into folder 1324 on the core server and launched the application by clicking on roon.exe file. I then went to my second server (bridge) and opened folder 1311 and clicked on relaunch.exe file which brought that online as well bringing my iphone and ipad ARC app and ROON app (which I use to control zones) back online. Hangin with this work around until the next update comes out.
This is UAT - User Acceptance testing. When we do software development, first we must pass the Implementation lab for Performance and major bugs, from there, UAT. Then, we have two Production Lanes, PL1 and PL2. This is two segments of somewhat knowledgable technical users who we’ll task to focus on two different aspects of the Prod build, before we finally move out to GP - General Production. Depending on the disposition of your DEV team, iLab to GP should take about a week for incremental upgrades, three weeks to a month for major iterations. The resulting user satisfaction of sticking to this dev process is a MASSIVE win for happy customers.
