I don't know why anyone would want a natural language description of user visible changes in a release.
The convention that worked where I worked was to praise the first line of such changes prefxed with "uv:" which would become bullet points for the changelog. Rarely would any need to be rewritten except for fixing the odd typo or punctuation.
Comments
I don't know why anyone would want a natural language description of user visible changes in a release.
The convention that worked where I worked was to praise the first line of such changes prefxed with "uv:" which would become bullet points for the changelog. Rarely would any need to be rewritten except for fixing the odd typo or punctuation.
Well, I guess it depends. In my case, our PR department asked if there was something similar to a devlog, there wasn't so I made it