-
Notifications
You must be signed in to change notification settings - Fork 28
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
Confirm go-cose v1.0.0-rc.1 is ready for a 1.0.0 release #37
Comments
@SteveLasker We are building and testing COSE support for notation, which can be tracked at
|
@shizhMSFT, excellent! As we get cose integrated in a notation build, we'll start having users validate MAR content. At that point, we should have good validation. We're doing our best to not release 1.0, then have a 1.1 release because folks hadn't fully tested the rc.1 release. |
@SteveLasker Let's release go-cose 1.0 after merging the COSE support for notation. /cc @yizha1 @FeynmanZhou |
Once COSE support is merged into notation main branch, we could invite users to verify it for an E2E flow. Based on the results we will be more confident on go-cose 1.0 release. |
@SteveLasker Can we cut a |
go-cose v1.0.0-rc.2 is available: https://github.com/veraison/go-cose/releases/tag/v1.0.0-rc.2. I think we can start to update the dependency version of go-cose to v1.0.0-rc.2 here. |
I think |
@SteveLasker The go-cose v1.1.0 is already supported, so this Issues should be closed. |
Thanks @fanndu Closed as https://github.com/veraison/go-cose/releases/tag/v1.1.0 was released |
The go-cose project is pending a 1.0.0 release
Before cutting the release, they (me) are asking for dependent projects to confirm confidence in the current 1.0.0-rc.1 release before cutting the 1.0.0 release.
Have we completed our testing for notary cose support? Once we have, we would add a +1 from notary on the Create 1.0.0 Release #98 issue
The text was updated successfully, but these errors were encountered: