Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve release management #16

Open
przemoc opened this issue Feb 11, 2018 · 6 comments
Open

Improve release management #16

przemoc opened this issue Feb 11, 2018 · 6 comments

Comments

@przemoc
Copy link

przemoc commented Feb 11, 2018

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.
@QuLogic
Copy link

QuLogic commented Mar 26, 2018

Also, the code uses autotools and (correctly) does not include the generated files in git. However, to limit the need for end users to need autotools, the tarballs should include the generated files (which they currently do not.)

@veorq
Copy link
Member

veorq commented Mar 27, 2018

Thanks guys, not much time on my side, trying to find help :-)
https://twitter.com/veorq/status/978538671929462784

@sneves
Copy link
Member

sneves commented Mar 27, 2018

I've added 0.98 tag and a degitified make dist release to the releases Github page.

@QuLogic
Copy link

QuLogic commented Apr 5, 2018

Adding a pkg-config file would be useful too (though everything is mostly in a standard location anyway.)

@ThomasWaldmann
Copy link

@QuLogic i just added #22 before reading your comment.

on some OSes / dists, stuff is not at standard locations (e.g. nixos, haiku).

also, when wanting to switch to pkg-config as an application which uses some libs, it would be great if all of them supported it, so all stuff can be dealt with in the same way.

@ThomasWaldmann
Copy link

@QuLogic can you review/test #23 ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants