Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Create 1.0.0 Release #98

Closed
3 tasks done
SteveLasker opened this issue Aug 12, 2022 · 10 comments
Closed
3 tasks done

Create 1.0.0 Release #98

SteveLasker opened this issue Aug 12, 2022 · 10 comments
Assignees
@qmuntal @thomas-fossati @yogeshbdeshpande @shizhMSFT @roywill
Milestone
1.0.0

Comments

@SteveLasker
Copy link
Contributor

SteveLasker commented Aug 12, 2022 •
edited
Loading

Complete the 1.0.0 release

High-level deliverables as follows:

  • Decide on main commit for a release (c5ba0da)
  • Cut a tag named v1.0.0
  • Update README.md

Before we ask for a +1 to cut the release, we're asking for a few of the dependent projects to confirm rc.1 is ready for a 1.0.0 release

Can the maintainers please respond with a +1 comment once you are in favor of cutting this release?
@SteveLasker SteveLasker added this to the 1.0.0 milestone Aug 12, 2022
@SteveLasker SteveLasker mentioned this issue Aug 12, 2022
Closed
@SteveLasker
Copy link
Contributor Author

Noting: notaryproject/notation-core-go#37 (comment) as confidence in the 1.0 release. There are some new feature requests, but these could come post 1.0. Providing a solid 1.0, with 2 public security reviews completed, speaks to our readiness.

@thomas-fossati
Copy link
Contributor

We have been using the v1.0.0 release candidate in four different places for a while now, and there has been no problem except for #115 which is now fixed in the main branch. We are confident that main (c5ba0da) is ready to ship.

@roywill
Copy link

roywill commented Jan 12, 2023

We should release.

@SteveLasker
Copy link
Contributor Author

@veraison/go-cose-maintainers, can you please give a +1 to cutting the 1.0 release based on c5ba0da?

@SteveLasker
Copy link
Contributor Author

+1 to release, based on c5ba0da

@yogeshbdeshpande
Copy link
Contributor

+1

@roywill
Copy link

roywill commented Jan 18, 2023 via email

@SteveLasker SteveLasker mentioned this issue Jan 18, 2023
Closed
4 tasks
@SteveLasker
Copy link
Contributor Author

🎉 v1.0.0

@SteveLasker
Copy link
Contributor Author

Remaining PR to update the readme: #121

@SteveLasker
Copy link
Contributor Author

Closing as 1.0 is released, and the readme is updated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@qmuntal qmuntal

@thomas-fossati thomas-fossati

@yogeshbdeshpande yogeshbdeshpande

@shizhMSFT shizhMSFT

@roywill roywill

Labels
None yet
Projects
None yet
Milestone
1.0.0
Development

No branches or pull requests
6 participants
@qmuntal @SteveLasker @thomas-fossati @yogeshbdeshpande @shizhMSFT @roywill