You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's not entirely bad because usually this is also shown with the date of last release or the list of recent releases, which will obviously be fresher:
...but it probably causes people to miss new features or think the project is not as maintained as it otherwise is.
The text was updated successfully, but these errors were encountered:
Any suggestions how to fix this?
Since the changelog markdown gets pulled into the marketplace that seems kinder important to keep up to date. Should we just use that and nothing else? Or maybe we should still use our purple request changes and then used a changelog markown as our release notes that we create periodically?
To be honest we haven't really been that good with doing release notes in the past and I'm not to optimistic about the future either. I'm more tempted to just use the changelog markdown and nothing else.
I'm happy to take on writing more of the release notes going forward, I like that kind of thing and I think it's good to get the maximal value for the work that all of the contributors have done.
We have a few places where we put release notes:
However CHANGELOG.md is used on the marketplace:
and when you go to install an extension:
It's not entirely bad because usually this is also shown with the date of last release or the list of recent releases, which will obviously be fresher:
...but it probably causes people to miss new features or think the project is not as maintained as it otherwise is.
The text was updated successfully, but these errors were encountered: