-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release notes improvements #212
Comments
Thanks for the suggestion. I don't like changelogs where you don't know exactly what changed in your current version because they just list a bunch of versions (unless there are unreleased/partially release versions since the last change). However having a link to the full changelog might be an interesting idea. |
The list of changes in
Another wording could be:
|
I saw you added a link to the AMO version history already. 👍 And thanks for the contributor update. :) |
This is gone now again. Only the most recent change is displayed and one has no easy way to catch up on former changes. With v1.8.0 I only get this now: It used to have a link to https://addons.mozilla.org/en-GB/firefox/addon/advanced-github-notifier/versions/. |
Yes, I didn't add the link in the 1.8.0 release notes. I have to add it to every version manually if I want it to be there. And honestly I'm mostly waiting on the upstream fix for it (one day I might be tempted to do that one myself if it doesn't move at all) |
It seems I haven't linked the upstream bug here yet, it's https://bugzilla.mozilla.org/show_bug.cgi?id=1688045 |
Makes totally sense! Thanks for taking care of the bug report (and linking it). 👍 |
Most users have auto update enabled and don't review/check all changes.
Due to the
Release Notes
only showing the most recent change(s), features or important changes are easily missed:It would be helpful to have a Changelog with version numbers and some simple history there like:
Or a link to a changelog file or e.g. the GitHub Releases page or the Mozilla Add-On version history
The text was updated successfully, but these errors were encountered: