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

okpy.org migration process #221

Closed
8 of 9 tasks
knrafto opened this issue Sep 1, 2016 · 0 comments
Closed
8 of 9 tasks

okpy.org migration process #221

knrafto opened this issue Sep 1, 2016 · 0 comments

Comments

@knrafto
Copy link
Contributor

knrafto commented Sep 1, 2016

The server is running on both https://ok.cs61a.org and https://okpy.org currently. Due to SSL issues, some clients cannot connect over https to ok.cs61a.org and therefore cannot automatically update.

Deployment process:

  • Merge Use okpy.org domain #220 to use okpy.org domain and to change ok-client's self-reported version to be 1.6.14 (the latest release)
  • Upload release to pypi as 1.6.14-1
  • Edit the 1.6.14 release to have the new ok-client binary
  • Update the berkeley-cs61a requirements.txt to use pypi version 1.6.14-1. All new assignments, starting with lab02, will use the new version. The new clients will not attempt to update, since they believe their version is still 1.6.14, and the ok server reports the latest version as 1.6.14.
  • Verify that the new version works for students who previously had SSL errors
  • Wait for all assignments that were released before lab02 to be turned in. This should be a few days after 9/8, when Hog is due.
  • Bump the version number to 1.7.0
  • Edit setup.py to use the real version number again
  • Deploy the new version normally (to pypi, GitHub, okpy.org, and berkeley-cs61a).
@knrafto knrafto closed this as completed Sep 13, 2016
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

1 participant