@manics suggested we get windows support for jupyter-server-proxy's next release, which requires this project to get #26 merged and then a new release made.
I suggest we go for 1.0.0 after getting a few things done, where I propose 1.0.0 over 0.5.0 in order to arrive to 1.0.0 where choosing future versions is far easier based on the semver2 meaning of major.minor.patch version identifiers.
@manics suggested we get windows support for jupyter-server-proxy's next release, which requires this project to get #26 merged and then a new release made.
I suggest we go for 1.0.0 after getting a few things done, where I propose 1.0.0 over 0.5.0 in order to arrive to 1.0.0 where choosing future versions is far easier based on the semver2 meaning of major.minor.patch version identifiers.
PRs in need of review
26
29
30
31
Issues to resolve
35