Skip to content

Consider tagging releases #13

@n-peugnet

Description

@n-peugnet

Hi, I packaged your library in Debian, and it is considered good practice to use tagged releases. Here are the Go official recommendations: https://go.dev/doc/modules/version-numbers

Since your package seems quite stable you can consider tagging the current version with v1.0.0. If you want to keep the liberty to change the API, you should use an unstable version number like v0.1.0.

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