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

Automate stable release workflow #6628

Open
NoureldinYosri opened this issue May 31, 2024 · 1 comment
Open

Automate stable release workflow #6628

NoureldinYosri opened this issue May 31, 2024 · 1 comment
Assignees
@xXxH3LIOSxXx
Labels
area/releases good first issue This issue can be resolved by someone who is not familiar with the codebase. A good starting issue. kind/health For CI/testing/release process/refactoring/technical debt items no QC knowledge needed Want to contribute to Cirq, but don't know quantum computing? This issue is for you. triage/accepted there is consensus amongst maintainers that this is a real bug or a reasonable feature to add

Comments

@NoureldinYosri
Copy link
Collaborator

Description of the issue
The release process for stable cirq verions is currently a manual process documented in https://github.com/quantumlib/Cirq/blob/67090465ba60a1ba1fdb8926defa3a465d52cc22/release.md. This documentation is out of date because of changes to the underlying tools.

The release process doesn't have to be manual. we already automate the prelease process which packages and uploads cirq to pypi after each PR merge https://github.com/quantumlib/Cirq/blob/main/.github/workflows/release-main.yml.

A similar workflow should be created that gets triggered by a github realease ... that's the process for creating a stable release shoudl be just a two step operation: 1. update the cirq version 2. create a github release (Which triggers the realease workflow) which is what we do for other quantumlib libraries like QSim https://github.com/quantumlib/qsim/blob/master/.github/workflows/release_wheels.yml
@NoureldinYosri NoureldinYosri added kind/health For CI/testing/release process/refactoring/technical debt items area/releases labels May 31, 2024
@NoureldinYosri NoureldinYosri added triage/discuss Needs decision / discussion, bring these up during Cirq Cynque good first issue This issue can be resolved by someone who is not familiar with the codebase. A good starting issue. no QC knowledge needed Want to contribute to Cirq, but don't know quantum computing? This issue is for you. labels Jul 3, 2024
@xXxH3LIOSxXx
Copy link

@NoureldinYosri - Here!

@NoureldinYosri NoureldinYosri added triage/accepted there is consensus amongst maintainers that this is a real bug or a reasonable feature to add and removed triage/discuss Needs decision / discussion, bring these up during Cirq Cynque labels Jul 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@xXxH3LIOSxXx xXxH3LIOSxXx

Labels
area/releases good first issue This issue can be resolved by someone who is not familiar with the codebase. A good starting issue. kind/health For CI/testing/release process/refactoring/technical debt items no QC knowledge needed Want to contribute to Cirq, but don't know quantum computing? This issue is for you. triage/accepted there is consensus amongst maintainers that this is a real bug or a reasonable feature to add
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@xXxH3LIOSxXx @NoureldinYosri