Closed cweiske closed 6 years ago
I’ve been tagging releases with the git CLI. Should I do this through the Github interface instead (i.e. uploading the zip file manually)?
I thought we discussed this somewhere at one point, but I lost track of that, wherever it was.
If I checkout a git tag, I still need to compile the JS and such. The .zip file that you upload to the play store or mozilla addons page can be used directly, which is why having that in the releases (manually uploaded or via API) would be nice.
Oh, I see. You want me to make the zips available for download somewhere?
There are all archived in the zips folder, but I could expose that better somehow.
I do not think that distribution files should be part of the source code repository itself. -- Regards/Mit freundlichen Grüßen Christian Weiske
Provided with v1.0.0. I’ll try and do this from now on with all future releases. I’m also making these available for download from the release notes page on omnibear.com.
Instead of providing the source code as .zip in the github releases section, please provide the compiled extensions so that one can install them without using the stores.