Why are automatic updates done that contain "Stable Release Candidate" code? Why not wait until that version of code has hit Stable? And, I don't really care to hear the "oh Meraki Release Candidate code is different talk"... if it truly was that different, then why is not changed to a Stable Release vs. Release Candidate. This would be OK if more information would be outlined in the release notes for that code, many times we have tried Release Candidates only to come across an issue that was known but not explained in the release notes, however is address in the Stable Release. If you plan on pushing auto-updates to our networks, give us an option to only allow code that is in the Stable branch.
This document describes the firmware release cycle.
What it doesn't mention is that a certain percentage of devices globally have to be running a specific release, with minimal issues, before it can be promoted to a "stable" release.
So if no one upgrades, it can never be declared a stable release.
Because the stable release canidate is being pushed out now, the chances are it will push over that threshold soon, and that same release will get declared "stable".
I’ll be very blunt on this issue. I have no problem with receiving the notice for auto firmware updates, but only if the release is marked as Stable. We should have an option to only allow the network to auto update if the Stable track is being pushed. No more, no less.
A bit like the multiple upgrade tracks with Windows?