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.

Sign up for GitHub

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

Jump to bottom

GitHub Releases #430

Closed
cinemast opened this issue May 29, 2015 · 5 comments
Closed

GitHub Releases #430

cinemast opened this issue May 29, 2015 · 5 comments
Labels
Tweak request

Comments

@cinemast
Copy link

Hi!

First, great software. Thank you for developing and maintaining it.

Could you please create regular releases for your software? GitHub provides that automatically if you just use tags to mark your versions.

https://wiki.debian.org/Creating%20signed%20GitHub%20releases

That would be great.
@DavidEGrayson DavidEGrayson mentioned this issue Jun 25, 2015
Closed
philsquared added a commit that referenced this issue Jun 29, 2015
@philsquared
Committed to semantic versioning
21f7ef6 
as prompted by #365, #430, #447 and a thread on the google group.
- split version bumping out of generateSingleHeader script
- separate scripts for bumping each version component
- "build" number only incremented for "develop" builds
@philsquared
Copy link
Collaborator

Sorry for not getting back sooner. I've done a bit of tweaking to support Semantic Versioning and am now tagging "release" commits.

@cinemast
Copy link
Author

Great, thank you!

Could you also take a look about signing releases using GPG/PGP? That would be great.

@philsquared
Copy link
Collaborator

I'll look into that @cinemast - looks like quite a bit of work to get set up

@cinemast
Copy link
Author

I get that. But I really put more screenshots in there than required, to make everything as clear as possible.

Basically its:

  • Generate a gpg key
  • download/create tarball
  • sign it using gpg
  • upload signature as attachment to the release.

If you have any questions, just conact me (also off list, my mail is on my github account site).

Thanks for considering it.

@horenmar
Copy link
Member

Well it took a while but the latest release is properly signed*

* In that the constituent tag and released headers are signed, I am not planning to be signing the tarball as it is not intended for distribution.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Tweak request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@philsquared @cinemast @horenmar