Thanks for this Brandon. What I can tell you is in this case there wouldn’t have been an associated release note because the change wasn’t supposed to have gone out (until today, actually, see here: 8.23 Release Notes - #12 by lampronf).
Generally speaking we’re trying to move away from features tied to specific point releases (for various reasons, but a big one is so that we can immediately roll back changes when we have to, as was done in both the instances you mentioned). We’re aware that makes it difficult to stay on top of what’s new, but what we’ve started doing to try and make up for that are a few things:
- Targeted in-app messages to highlight new feature releases
- Activating larger new features with specific timings (so we might deploy the code in an earlier version but not actually enable them right away) and then having some communications in advance of that
- Ensuring that the release notes for each new point release also capture anything significant that went out in the previous release cycle (see here for example)
That’s not to suggest this is a perfect system of course, thanks for keeping us honest, and we do appreciate any further feedback or suggestions you might have to make this better. Ultimately we want to provide updates that help you do your jobs both in a timely and non-disruptive way, and we want you to know about them!