-
Notifications
You must be signed in to change notification settings - Fork 289
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
Tracking release 7.0 changes #642
Comments
Here's an attempt to document the API changes mostly brought about by the Kernel Provisioning changes (#612). This content will need to be relocated but I wanted to get an initial form persisted somewhere. API ChangesAll of the API changes for
|
I'm working on the |
RC coming tomorrow morning US time. |
Let's aim for a final release on Mon Aug 16 |
Let's hold off on the release until #644 is finished |
Looks like we're good! I'll handle the changelog and cut the release after getting lunch. |
Since we will be delivering a major release (7.0), I'm hoping we can use this issue to track changes that might affect existing applications. We should, at this time, go ahead and remove deprecations that have been in place as well as other api-changes (preferably minor in nature).
kernel_cmd
trait ([Release 7.0] Remove deprecations in kernel manager #643)cleanup()
method ([Release 7.0] Remove deprecations in kernel manager #643)block
parameter fromget_msg()
(Remove block parameter from get_msg() #671)KernelSpecManager.whitelist
trait toallowlist
,allowed_kernels
, ?The following are needed for Kernel Provisioning. If Kernel Provisioning is not in the initial 7.0 release, it would be good if these could be included in 7.0, to enable Kernel Provisioning's introduction in a minor release:
async
(usingrun_sync
for non-asyncKernelManager
):request_shutdown()
pre_start_kernel()
post_start_kernel
cleanup_resources()
restart=False
parameter to the following kernel manager methods:_async_finish_shutdown()
._async_send_kernel_sigterm()
._async_kill_kernel()
.We should probably talk about branching as well. I guess we'll keep working off the tip and create a 6.x branch against the appropriate tag once a 6.x PR is required.
The text was updated successfully, but these errors were encountered: