-
Notifications
You must be signed in to change notification settings - Fork 26
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
Cut an v1.0.0-alpha.1 release #12
Comments
Are we ready to cut the first alpha release? |
@SteveLasker Should we just version it |
+1 so long as we have clarity and consensus on the release tag |
so, we agreed on doing semver, right? |
v1.0.0-alpha.1 would make sense here. I was mixing other projects. |
@yogeshbdeshpande, @shizhMSFT, @henkbirkholz can you reconfirm the |
+1 from my side. I think, lets stick with v1.0.0-alpha.1 version and close this issue! |
+1 for release |
With #65 complete, closing this issue |
As we start to take dependencies on go-cose, we should cut a versioned release, and define the release process.
Adding a link to veraison/community#4 for defining a process.
v1.0.0-alpha.1
based on agreed upon main commitv1.0.0-alpha.1
v1.0.0-alpha.1
The text was updated successfully, but these errors were encountered: