Closed consideRatio closed 1 month ago
great
Which of these do you consider blockers for 2.0.0?
I'm not sure, but I'd like to keep going a while and when I run out of steam try to answer that with a better overview.
Here are things I'm currently thinking truly must resolved before 2.0 @manics:
Currently blocked by review input.
allowed_users
etc function side by side with allowed_groups
etc - can they be used together, and if not, is it a breaking change to fix it? If so, we should fix it now.I think we should resolve the following as well, but they could come in a followup minor release as well.
Simple to fix, I'll get it done. Its not truly a blocker, but its such a clear bug that has a simple fix making me want to get it part of the next release.
Thanks for leading all this! I can have a stab at #246. allow config is very likely the cause.
When this is ready do you think we could release a beta first, to give more time for reviewing the authenticator as a whole, especially after the security changes?
Let's do a beta release to be part of tljh / z2jh beta releases, where kubespawner probably needs a beta release as well for z2jh
2.0.0b1 is released!
Having worked in this code base a while and read all issues, I have a few ideas of improvements still:
I think we can go for a 2.0.0 release now, the beta has been tested a bit already with no red flags I think.
This is a dependency of z2jh and tljh that hasn't been updated in a long time. I'd like to get one release out that is known to work with jupyterhub 4 at least.
Action points
221 (actually merged, github just bugged!)
222