Zero-to-jupyterhub-k8s: Plan for v0.7 release

Created on 31 Mar 2018  路  6Comments  路  Source: jupyterhub/zero-to-jupyterhub-k8s

0.7 Release - Post PEARC Pre JupyterCon

  • [x] JupyterHub 0.9.1
  • [x] An updated pre-puller logic

Save for 0.8:

  • [ ] A two node-pool setup for core-pods and user-pods
  • [ ] A custom scheduler for user pod packing on nodes
  • [ ] user-placeholder pods to create headroom for real users
  • [ ] user-dummy pods to allow for easy verification of autoscaling behavior

We released v0.6 on Jan 30, and so should try to make a v0.7 release sometime in the next few weeks! I think we're in a reasonably stable state to make it happen.

There are instructions in https://github.com/jupyterhub/zero-to-jupyterhub-k8s/blob/master/CONTRIBUTING.md#releasing-a-new-version-of-the-helm-chart on how to make a release. It would be great if we could spread out 'who is doing the release' some more! So hopefully we can make this release happen without my involvement :)

List of 0.7 milestones: https://github.com/jupyterhub/zero-to-jupyterhub-k8s/issues?q=is%3Aopen+is%3Aissue+milestone%3A0.7

Most helpful comment

Wait, what? You started a job as a data engineer? That's awesome @consideRatio !!! Congrats!!!

Anybody else have thoughts on v0.7? @minrk? I'll ping @yuvipanda though I think he is gonna be offline for the next couple of weeks.

All 6 comments

Will this release contain an updated base-notebook container version?

How are we doing on this? Should we try to push out v0.7 before conference season hits?

@choldgraf I'm dead set on having a release before JupyterCon (21-24 Aug) containing some features I've been working on related to autoscaling, it can be a 0.8 release as well though. PEARC (22-26 Jul) is earlier.

I've just started a new job as a Data Engineer and I get to spend quite some time working on z2jh as compared to only doing this on my spare time. I'm making quite quick progress but it is a lot of documentation left to do after I've got the code in place.

Perhaps we could push out 0.7 for PEARC, then 0.8 with additional features in the pipeline for JupyterCon? Various things I'm testing right now require k8s 1.11 to be activated anyhow.

I updated the first entry.

Wait, what? You started a job as a data engineer? That's awesome @consideRatio !!! Congrats!!!

Anybody else have thoughts on v0.7? @minrk? I'll ping @yuvipanda though I think he is gonna be offline for the next couple of weeks.

@choldgraf thank you! It is actually all thanks to you in the JupyterHub team welcoming me to be a member! :heart:

Features I'd like to add for 0.7 / 0.8, before JupyterCon!

ca

Was this page helpful?
0 / 5 - 0 ratings