-
Notifications
You must be signed in to change notification settings - Fork 287
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
Patch release for 5.x (5.3.1) #458
Comments
No objection here. As long as we've tested it out (since there wasn't a unittest involved) I'm ok with a patch release. |
|
@MSeal it seems that the changelog was not committed to https://github.com/jupyter/jupyter_client/blob/5.x/docs/changelog.rst Did you miss a commit or should I add it before pushing the new release? |
Hello - We're seeing issues in our Enterprise Gateway tests that we finally equated to 5.3.0 as well (once we reverted to 5.2.4 all was good again). I'd be happy to take the patch for a spin prior to 5.3.1. Is this a matter of building with #456? |
@kevin-bates yes! or rather the backport #457. |
@SylvainCorlay Ahh I missed making that commit. This repo doesn't have written down release instructions so I was running a similar project release pattern. Please do the other release note if you don' |
Our tests are passing again with the latest incantation of the |
Yeah! |
@MSeal could you add me to jupyter_client on pypi? my user name is |
I actually don't have that permission flag to manage users on this package PyPI. @rgbkrk might be able to help. Otherwise I can push out the 5.x branch if you've updated the commits on that branch if you want me to help for today. |
Thanks! Please go ahead and publish the package. Will be very happy to see my tests pass again :) |
@MSeal let me know if you find the moment to push the release out! |
I can do it in an hour or two when I get back to a computer
…On Tue, 9 Jul 2019, 3:19 PM Sylvain Corlay, ***@***.***> wrote:
@MSeal <https://github.com/MSeal> let me know if you find the moment to
push the release out!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#458?email_source=notifications&email_token=AAOHBVED7SYZD6KYUELPP3TP6UFFXA5CNFSM4H7IWSJKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZRWPRQ#issuecomment-509831110>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAOHBVE2ZOT2CK65HG5S3OTP6UFFXANCNFSM4H7IWSJA>
.
|
@Carreau could give me the permission and I was able to push the packages! |
@SylvainCorlay I don't have any objection. It would probably make sense to do another 5.3.2 beta after this (maybe at the sprints) to make sure that all things are working for the other projects as well as the docs being up to date. Thanks for pinging me on the issue too. |
We should also make sure the conda-forge recipe is up to date too. |
Yes, the test to reproduce the failure that we encountered in voila would be rather hard to do, but there are some sanity checks that we could add and would have prevented it. 5.3.1 is out! |
If you can add me as a maintainer on pypi too, that would be great. |
PR on the way. |
(weird how github handles async messages). So I was added as a maintainer (not an owner) so I cannot add new maintainers. @Carreau shoud be able to do it. |
5.3.1 looks good. Thanks for the quick turnaround everyone! |
Great! Closing this. |
@MSeal @willingc @rgbkrk
do you have any objection with a patch release of jupyter_client (5.3.1) to include the fix for the kernel shutdown that was done in #456 ?
The text was updated successfully, but these errors were encountered: