VSCode is a good example. After the latest updates, the Recent Changes are surfaced when we open the editor.
That combined with a What's New? link should answer this question any time.
If the issue is customer/end-user view versus internal view of changes, you could put them in a separate section of the Recent Changes release note.
For status tracking in the pre-release/dev/testing stages (for eg., to answer your when is featureX shipping? question, wouldn't something like GitHub tags suffice?
Release Notes?
VSCode is a good example. After the latest updates, the Recent Changes are surfaced when we open the editor.
That combined with a What's New? link should answer this question any time.
If the issue is customer/end-user view versus internal view of changes, you could put them in a separate section of the Recent Changes release note.
For status tracking in the pre-release/dev/testing stages (for eg., to answer your when is featureX shipping? question, wouldn't something like GitHub tags suffice?