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
Is it possible to have a single, curated changelog file?
What I mean by curated: changes the maintainer deems significant? (e.g. breaking changes, features, bug fixes, package updates)
I suppose it's extra upkeep, but it's prohibitively difficult (if not impossible) as a user to paginate through releases and stay on top of what changed.😢 Only the maintainer can make sense of them - and even then may eventually forget what happened
The text was updated successfully, but these errors were encountered:
It's a open source after all, and I think it'd take up a lot of (more) of your time to manage a changelog file. Nobody (not me nor anyone else) is entitled to your time. Thank you once again for your project.
However, on the other hand:
I think that there's a general sustainability / practicality benefit to curating changelogs to a single file. It's more resilient to git (rather than github's proprietary way of doing things) and other potential future maintainers / contributors have a smoother time keeping up to speed. I think amortized it can save time. But fully up to you @chrisguttandin
Hi! Thank you for the project!
Is it possible to have a single, curated changelog file?
What I mean by curated: changes the maintainer deems significant? (e.g. breaking changes, features, bug fixes, package updates)
I suppose it's extra upkeep, but it's prohibitively difficult (if not impossible) as a user to paginate through releases and stay on top of what changed.😢 Only the maintainer can make sense of them - and even then may eventually forget what happened
The text was updated successfully, but these errors were encountered: