Make clear what a new release offers #276
Replies: 1 comment 2 replies
-
|
@1n3JgKl9pQ6cUMrW Thanks for bringing this up. Do you want to help rewriting them into a separate, more readable release note? |
Beta Was this translation helpful? Give feedback.
-
|
To be honest I did not even realize that file was there. It's almost the changelog I described in my proposal - so not much has to be done here. Maybe you can link it directly (or integrate) on the website? I use the site as a reference (for the API / events / options) and Git only for downloading the package (using the CLI, so I never see it in a browser). When there's a changelog on the site as well, things become much clearer :-) |
Beta Was this translation helpful? Give feedback.
-
|
@1n3JgKl9pQ6cUMrW There is already links to CHANGELOG on the website. |
Beta Was this translation helpful? Give feedback.
-
Is this a bug report?
No.
I am following this excellent plug-in for months now, but there is one thing that is a bit annoying;
It has "too many" updates following after each other.
I am using version 1.0.0 for about one week one (used 0.37 during bèta-testing of my own apps) and one week later we are already at 1.3.0
It's not the updates that are the issue, but the lack of information about every new version (sometimes there are two new versions a day).
Of course I admire the hard work, but maybe it's possible to publish an update-log or something?
Like with "real" apps?
Just show two or three highlights for every release, so one does not have to read the source-code or check every file-diff to see what has changed.
For most of us it's not always a good idea to update the plug-in with every release, because it can cause issues for the app itself (or production flow).
Version 1.1.0
November 21st, 2020
Version 1.0.0
August 27th, 2020
...something like that? It can be published on the site, so one can keep track on it.
Beta Was this translation helpful? Give feedback.
All reactions