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

Figure out how to handle upgrades of the default repo2docker environment #190

Open
moorepants opened this issue Sep 17, 2020 · 0 comments
Open

Comments

@moorepants
Copy link
Member

Textbook authors will write their books with Jupyter cells. They will get them to work with the current versions of software we have supported in the default-env. But we will want to upgrade default-env with new packages and new package version and even remove packages if we have to. This means we will break existing textbooks on these upgrades. We need to figure out a way so that authors of the textbooks are responsible for keeping their textbooks up-to-date with the upgrades to default-env, not us, as that workload is outside the scope of this team. Maybe we can simply leverage Delmar's team of students that are creating these textbooks to do the upgrades or maybe we need a way for authors to pin their textbooks to specific jupyterhub environment versions.

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

No branches or pull requests

1 participant