Wendy Gaultier
Wendy Gaultier
@blairdrummond The PR has not been created yet. It should be straight forward to create
We might want to pay a closer attention to this commit: https://github.com/StatCan/jupyter-apis/commit/863a996748b37e94aae013ea9de3d640af530423 It's the upgrade for 1.3.
We will also need to figure out what to do with the Golang Backend, and update the Build scripts accordingly
Need to decide if we merge it back into the kubeflow repo, or not. And write down the reason for/against. And the final decision. This will have a big impact....
Halfway done grouping the PRs together, will finish on Monday, and finish the table up to date (there was kubecost back too)
A new epic was created to handle those commits to redeploy. See https://github.com/StatCan/jupyter-apis/issues/131
A useful link to compare the version for 1.4 is : https://www.kubeflow.org/docs/releases/kubeflow-1.4/
Closing since we are going directly to 1.6 See https://github.com/StatCan/daaas/issues/1337 issue which replaces this one
## Backend After a quick chat with Will, it seems the way they have done the update previously is to launch the upstream jupyter-api, then open devtools and take a...
I will be going with option 1. Between the big changes they did it should be fast enough to do our own modifications on top. I will make the list...