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
After pushing to master, complete the following steps:
Change back to develop.
Remove the content of changelog (leave the heading).
Commit the file and push it.
A user doesn't sit and read every changelog that happen from every release. A user will read it when deciding to update. This is a problem when the changelog only contains the latest update.
Consider the following:
User has version 1.5.0.
Current release is 2.1.0.
Changelog will now only contain updates from 2.0.x to 2.1.0.
This is how the changelog was originally. However when we implemented github releases we made appveyor read the content of the changelog and add it to the release. A workaround would be to add a (temporary?) file with the current changes for the release and have appveyour attach these instead.
Changelog history is deleted after every release.
From current README.md:
A user doesn't sit and read every changelog that happen from every release. A user will read it when deciding to update. This is a problem when the changelog only contains the latest update.
Consider the following:
User has version 1.5.0.
Current release is 2.1.0.
Changelog will now only contain updates from 2.0.x to 2.1.0.
User is now 😥
Possible implementations 1 2
The text was updated successfully, but these errors were encountered: