Skip to content

Update Changelog for v1.1.0 #69

@tajmone

Description

@tajmone

Before merging release v1.1.0, update tha Changelog section in the main README.

The changes of the following Issues and commits between the previous release and the upcoming one need to be documented:

This Issues and commits concern minor changes that might not be worth documenting at all (maybe just provide a quick link to the Issue), so let's keep them in a separate list, as a reminder, until a decision is made:

Some of the above Issues are already closed and dealt with. I've postponed updating the Changelog because I haven't yet decided how detailed it should be — whether I should just group the changes into macro categories like "Typos", "Code Fixes", etc., and just link to the various Issues, or whether I should cover the details.

I won't be able to decide until I have the big picture of all the changes that made it through to v1.1.0.

Metadata

Metadata

Assignees

No one assigned

    Labels

    📚 CHANGELOGDocumenting changes between releases📋 check listThings to check before merging new release.🕑 pending decisionIssue requires decisions by maintainers

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions