Please create proper release tarballs

[lundmar]

Moving to github is great 👍 but please don't let that stop you from creating proper release tarballs. Meaning tarballs which include a ready to use configure script and not those half baked auto generated tarballs that github produces. Please use that sweet 'make dist' and upload the tarball as part of the github release notes.

Thank you.

[brarcher]

I think that all the release since the move to GitHub (e.g. 0.10.0) also included a tarball generated using the dist make target. The 0.10.0 tarball can be found in the Release section:

Did I miss a release at some point which did not have a tarball? I certainly plan on providing tarballs for releases. Or, is your comment really "please keep it up"? If so, will do!

[lundmar]

First, my apology - you have indeed released a proper tarball 👍
In my hurry I didn't read the release note but went straight to the listed files in the Downloads section of the release note - where releases are usually attached. Obviously I didn't notice the tarball link embedded in the release note.
Sorry, keep up the good work 😄

[brarcher]

Hm, I see how the Downloads section at the bottom can be confusing. I'm not sure how to disable that, as it seems that GitHub is automatically adding it. If you happen to know a way, please let me know and I can look into it.

[lundmar]

Since it is not possible to remove the Downloads section I think your best option is to simply to use it and attach the release file there instead of the custom link. Also, you might want to consider making signed releases (as supported by github) and attach eg. a check-0.10.0.tar.gz.asc file so that users and package maintainers can verify origin.

[brarcher]

Your comment about supporting signed releases is a good idea. I've added #52 to track it.