Skip to content

Can changelogs be bad? / Ignoring Deprecations #649

Open
@PhilLAL

Description

Hi,
thank you for this good practices you'va gathered.

While reading https://keepachangelog.com/en/1.1.0/#bad-practices, in

When people upgrade from one version to another, it should be painfully clear when something will break. It should be possible to upgrade to a version that lists deprecations, remove what's deprecated, then upgrade to the version where the deprecations become removals.

If you do nothing else, list deprecations, removals, and any breaking changes in your changelog.

I do not understand what means It should be possible to upgrade to a version that lists deprecations, remove what's deprecated, then upgrade to the version where the deprecations become removals.

Does it mean the following?

It should be possible to consecutively upgrade to a version giving a list of deprecations, then remove what's deprecated, and then upgrade to the version where the deprecations become removals.

Regards

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions