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
I've noticed my changelog has grown to several thousand lines. While I don't find this problematic from an editing perspective (I typically work at the top of the file, and the reference links at the bottom are automatically managed), I was surprised to find no explicit guidance in the keep-a-changelog FAQ addressing this situation.
I'm curious about community standards regarding pruning historical entries. Is there value in retaining very old release information, such as a v1.0 from 5+ years ago? I'd appreciate insights on best practices and whether there's a consensus on how to handle increasingly lengthy changelog files.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
I've noticed my changelog has grown to several thousand lines. While I don't find this problematic from an editing perspective (I typically work at the top of the file, and the reference links at the bottom are automatically managed), I was surprised to find no explicit guidance in the keep-a-changelog FAQ addressing this situation.
I'm curious about community standards regarding pruning historical entries. Is there value in retaining very old release information, such as a v1.0 from 5+ years ago? I'd appreciate insights on best practices and whether there's a consensus on how to handle increasingly lengthy changelog files.
Beta Was this translation helpful? Give feedback.
All reactions