-
Notifications
You must be signed in to change notification settings - Fork 133
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
Release 2.0 #242
Comments
For a major release, we should consider #229 as well. |
Fine by me. I'll tag it 2.0. Are you cool with moving #211 out of the 2.0 milestone? |
Yes, that's fine with me. |
How much extra effort would it be to release 1.2.2 alongside 2.0? |
It's not too much effort. I'm happy to do it. I'll send PRs for that branch. I think there's a backport missing for a duplicate deserialization bug fix that has to go into that branch too. |
@rolweber I tagged and pushed 1.2.2 off the 1.2.x branch. It should be on pypi. Do you also need a conda-forge package built for it? I haven't done multi-branch conda-forge builds, but I hear it's possible by creating branches in https://github.com/conda-forge/jupyter_kernel_gateway-feedstock |
@parente: Great, thanks! PyPI is sufficient for now. One small nuisance though: PyPi now considers 1.2.2 to be the "latest version". |
Ah. I can fix that. I can also grant you permission to manage it if you'd like. Create an account on pypi and let me know your username if you are interested. |
@parente: Great, thanks! I registered at PyPI as 'rolweber'. |
@rolweber I've added you as a maintainer on pypi. One of these days when we cut a new release, I can take you through the steps if you're available. |
Let's discuss making a 2.0 release. Here's things I think need to get done vs those that can be moved out:
TODOs
What do folks think? @rolweber?
The text was updated successfully, but these errors were encountered: