Thanks to the Meraki team for adding that, it shows once again that the community is integral to the solution 👍
For completeness below are the notes including half a dozen MS390 fixes:
The bullet was with regards to @cmr s work of sorting the change log by model.
So glad they adopted this, thanks cmr. Like many I've been having a difficult time reading through switch firmware changelogs. As someone who isn't using a MS390, it's been challenging to try and just focus on the details relevant to my networks because of how much MS390 content has been in the changelogs lately.
I would love to see each section of the changelog arranged this way, or even the ability to just filter by model and only show the changes relevant to my networks.
I agree, filtering to just your products would be a great idea for sure!
And yet, because we have a bunch of MS390s... I like the "shame" factor of showing ALL THE BUG the MS390 still has. Especially when they put in the notes that the issue has been around since version 12. It makes me wonder / worry, will Meraki ever resolve these bugs? Do they care? Will they only resolve these bugs when they discontinue the MS390 and move on to something else?
It feels like Meraki's heart is not in the MS390... And I get it, it's a new unique model / platform (taking a Cisco switch and slapping Meraki code on it), so yeah, writing code for it is probably more challenging for sure.
But to have 10x the amount of bugs vs other Meraki switches is hard to accept as a customer, especially ~3 years into the deployment now.
Agreed, I've been terrified to do switch firmware upgrades lately. I keep holding out hope that they'll get to a point where things are at least stable for non-MS390 models but doesn't seem likely.