If
Why wasn't it included in MS15.22 . Don't get it
haha ! Had never heard of that one yet 😂
Good question! As MS 15 is currently in its General Availability (GA) phase, it is crucial to exercise caution when considering additions for subsequent GA releases. The utmost priority is to avoid introducing any changes that might inadvertently destabilize the system.
In this particular case, the severity of the issue appears to be relatively low, as the devices eventually authenticate despite the challenge. Therefore, the risk versus reward assessment leans towards a more cautious approach.
It is worth noting that the most recent beta/rc (release candidate) releases tend to include a higher number of fixes. This is due to the slightly higher tolerance for potential bugs that may emerge while attempting to address existing issues.
Rest assured, our team is committed to maintaining a robust and stable product, and we appreciate your understanding and support as we strive to continuously enhance its performance.
Wow ! Thanks a lot for that explaination. Let's say we are still on MS14.33 which is rock solid for us and that MS15 is in a GA phase , should we wait to jump to MS16 instead ? We have around 4K MS which we have to pilot and test a LOT of things and features. Trying to avoid to deploy MS15 and having to re-do all the testing for MS16 which sounds like is coming to GA late 2023.
I understand your concern about the potential impact on your organization's testing and deployment efforts. It's important to consider the specific needs and priorities of your organization when making decisions about software updates.
While MS 14.33 may be rock solid for you at the moment, it's worth noting that newer releases include important security patches and bug fixes. Waiting until MS 16 becomes GA might mean missing out on these critical updates for a longer period of time.
One approach you could consider is to evaluate the potential impact of upgrading to MS 15.22 by initiating testing of this version to simulate your organization's specific use cases and scenarios. This will help you determine whether the benefits of the new release outweigh the potential challenges of retesting and redeploying. While this may initially seem like a duplication of effort vs waiting for MS 16, it's important to recognize that testing MS 16 will build upon the foundation laid during the testing of MS 15. By thoroughly testing MS 15, you gain valuable insights into the potential impact of future updates, such as MS 16. This allows you to proactively address any issues, reducing the overall effort required when transitioning to MS 16.
Ultimately, the decision to upgrade depends on the specific needs and risk tolerance of your organization. Taking a cautious and well-planned approach to testing and deployment can help minimize disruption and ensure a successful transition to a newer release.