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.

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

Tagging releases #709

Open
nhey opened this issue Feb 7, 2024 · 2 comments
Open

Tagging releases #709

nhey opened this issue Feb 7, 2024 · 2 comments

Comments

@nhey
Copy link

nhey commented Feb 7, 2024

Would it possible for you to resume tagging releases to keep up with orbax-checkpoint and orbax-export on pypi?
Something like checkpoint-vX.X.X and export-vX.X.X would be helpful.

@cpgaffney1
Copy link
Collaborator

Sorry, don't quite understand the question. On PyPI, orbax-checkpoint and orbax-export are totally independent packages, so why is there a need for tagging there?

Also, you say "resume tagging releases" but I'm not aware that we've ever done this in the past?

@nhey
Copy link
Author

nhey commented Feb 7, 2024

Apologies for the lack of context. When you release a new version for orbax-checkpoint or orbax-export on pypi, I ask that you also create a git tag for the corresponding commit in this repository so that it is possible to identify the git revision for that version.

Releases were tagged on github until orbax split into two independent packages: https://github.com/google/orbax/tags and https://github.com/google/orbax/releases.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants