3 ms·
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? l
by vivegi 3y ago
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?
- v1l 3y agoHow much of what you're suggesting is kept manually up to date?
- vivegi 3y agoAll of it. It comes down to process followed by the dev team. But, it is done at the time of writing the PR or requirement. For eg: "Add paid subscriptions" feature request. If you have, say, a markdown document that outline the feature request, it would be a simple matter to have a script pull specific tags to build your release note. A ProdMgr would own the release note anyway. So, it doesn't really matter. My 2 cents, anyway. Others might have a different view.