Blog Post
Not to be pedantic but I was thoroughly confused for a moment here:
You have first bullet point:
- Communities will have two types of releases going ahead - Standard releases and Patch releases
Then in the next bullet point after:
All releases will be standard releases
So is there a Standard Patch then? Are Patches also Standard releases?
I kid, to an extent - but also, this probably could have been communicated more clearly. I was also unfamiliar with the term "out-of-band" which I looked up and is a telecom management style, and while I can read between the lines enough to determine that I am pretty sure you just mean "no set schedule" - it could have been phrased much more plainly so that anyone could understand it.
My most pressing piece of feedback here however is, two weeks between Stage and Prod deployment is a long time - we can't push updates between Stage and Prod when the versions are different. This doesn't go into how long between "Standard" releases, but if I assume that it will follow the previous monthly cadence, this mean that half the time we'll be in code freeze, and only have a two week window to deploy updates or changes across our instances. I hope that the news we're missing here is the update cadence changing somewhat, although that comes at the loss of more frequent updates. No matter which way this is read, it's disappointing.