Skip to content

Improve release management #16

@przemoc

Description

@przemoc

Please consider improving release management:

  • Use tags reflecting released versions of libb2.
    I advise using standard v<VER> style. (So latest one would be v0.98, pointing to commit 60ea749.)
    Then GitHub's tarballs (tar.gz) available in Tags page will be created just like using git archive --format=tar.gz --prefix="<REPONAME>-<VER>/" v<VER>. (So libb2-0.98 for latest one.)
    But if for some reason your official tarballs on blake2.net differ than those generated automatically using this method, then please upload them to the GitHub release too, so blake2.net won't be the only source of them.
  • Put all official libb2 tarballs in one place with directory listing enabled.
    Some suggestions: files.blake2.net, blake2.net/files/, blake2.net/dist/.
    It makes automated scanning for new versions much easier.
  • Do not include git repository data in libb2 tarballs.
    https://blake2.net/libb2-0.98.tar.gz (614300 bytes, last modified on 2018-02-02 13:04:19 UTC) that is currently available would be much smaller if generated in the standard fashion (~270 KB).
  • Make libb2 existence more official.
    Mention it and link to its latest tarball from the blake2.net front web page.
    libb2 is only mentioned in the context of Rust binding created for it.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions