Skip to content

Backport infra/ansible to r2.0 #5104

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

Merged
merged 1 commit into from
May 31, 2023
Merged

Backport infra/ansible to r2.0 #5104

merged 1 commit into from
May 31, 2023

Conversation

wonjoo-wj
Copy link
Collaborator

Backport infra/ansible to r2.0

@wonjoo-wj wonjoo-wj requested review from will-cromar and JackCaoG May 31, 2023 20:33
@JackCaoG
Copy link
Collaborator

@mateuszlewko FYI

@wonjoo-wj
Copy link
Collaborator Author

@JackCaoG, are we good on merging this to 2.0 branch? Or shall we wait on @mateuszlewko's input?

@wonjoo-wj
Copy link
Collaborator Author

Thanks for the approval, Jack. I'll merge this and update the v2.0.0 tag on the r2.0 branch.

@wonjoo-wj wonjoo-wj merged commit 500e1c2 into r2.0 May 31, 2023
@wonjoo-wj
Copy link
Collaborator Author

wonjoo-wj commented May 31, 2023

Updated the v2.0.0 tag on r2.0 branch with commands:

  456  git checkout r2.0
  457  git pull
  459  git tag -d v2.0.0
  461  git push origin r2.0 :refs/tags/v2.0.0
  462  git tag v2.0.0 500e1c27530a21408fbd181a7296eda9cdcbe834
  464  git push origin r2.0 v2.0.0

Now, we can see that the v2.0.0 tag corresponds to this commit -- https://github.com/pytorch/xla/releases/tag/v2.0.0.


Just for reference in case we want to undo this, the previous v2.0.0 tag was at commit 9d8446b.

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

Successfully merging this pull request may close these issues.

2 participants