I recommend waiting a month to install this update, due to Synology's egregious pattern of recalling updates and then re-releasing patched updates with the same build number.
When that happens, early adopters are unable to install the corrected patch. And we know that Synology's first patch release often introduce new deficiencies. I, for one, am stuck on a "release 2" version that was twice replaced. But I'll not repeat that, jumping to an early "release 3" build.
It's my hope that some here who have a relationship with Synology would use their influence to end this poor practice of releasing "patched" patches without advancing the build number.
Agree with Mr. T. I have encountered just what he has explained!!! A couple times!
P.S.: This is the second time in a week that DSM or SRM updates are posted here, first -- before seen at Synology Forum!!
Agreed, but due to recent MO by Syno when it comes to their patches, I never put new patches on day1 on PROD... just in case. Can't shake the feeling that this new "will be deployed in different regions..." policy means, let's buy some weeks by pushing the patch to the masses and see what will go wrong. Then we will patch some more and then we will do a mass rollout.
Well indeed. It's definitely worth reading the release notes to determine if it relates to anything you use... if you don't use a fixed/patched feature then probably it's worth not updating, at least not right away.
You know those bugs when the male often gets eaten by its mate: