-
Notifications
You must be signed in to change notification settings - Fork 6
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
Release tags discussion #38
Comments
For information I just prepped locally each and every tags of the baseline. I also signed them, so users know they can trust it. Regards, Edit: Out of curiosity I tested on my personal fork. It seems that the only thing needed to create tarballs are the tags. Github generated automatically tarballs and zips in the /release/ tab ! |
hi @GallaisPoutine, I think it is a good idea! It would be nice to have the release tag + do a cargo version update (which I think it is already required for some automated archlinux packaging thing for our project). As a second step we could also add binaries to the releases. I'll create one issue and if you feel like working on it go for it! Thanks for bringing this up |
@GallaisPoutine I created two issues, feel free to give your input there as well, I just tried to give some first guidance since I have good experience with devops/CI/CD. |
Hi @pedroscaff,
What are your thoughts on release tags ?
I'm thinking it could be a great way to automate deliveries, and source tarballs. I do not know how tarball releases can be automated, but this can be a first way to do this.
I am thinking of this kind of things:
https://github.com/OP-TEE/optee_os/tags
Regards,
Raph
The text was updated successfully, but these errors were encountered: