-
Notifications
You must be signed in to change notification settings - Fork 5k
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
Pre-release plan for Notebook v7 #6266
Comments
Thanks @Zsailer for opening this 👍 Probably the main issue with this approach will be RetroLab coming with the |
My suggestion was such that we might "get away" with a fair amount of reuse-by-extension, and not get have to get too crazy on it, but could it be its own (wrapper)
If all of these things are hardcoded all over, maybe this is a good time to push on this (and the lab 4 upstream). |
Last week, we discussed moving the development of retrolab to the notebook repo. This repo's I went ahead and created a |
Linking to jupyterlab/retrolab#323 (draft PR to get the CI checks) where some work has been started to make the transition. |
Posting here the steps to make the first v7 pre-release happen, as discussed yesterday during the weekly Notebook meeting:
|
Once we have a first prerelease out, we can close this issue and open a new "Notebook v7 Release Plan" issue. Or rename this issue to "Notebook v7 Release Plan" and continue here. |
I moved the checklist to the top-level comment for visibility, and added links to the relevant issues and PRs: #6266 (comment) |
What branch do we want to create?
More branches could still be created later on if needed. |
I created the 6.4.x branch already, a little over a month ago. 😃 Should we go with that? |
Thanks @Zsailer. I think this sounds good. This can be changed later if needed, in case there are plans to release a |
The remaining item for this issue is to actually make the pre-release. What do folks think about doing it with the current state of the Since the repo is compatible with the Jupyter Releaser, we can follow the regular process of a "Draft Changelog" followed by a "Full Release". |
Also I don't seem to have rights to publish to PyPI: https://pypi.org/project/notebook. So maybe @Zsailer would like to help with this, thanks! |
A follow-up would be to open a new "Notebook v7 Release Plan" issue to start discussing the timeline and items for 7.0 final. |
@jtpio I added you as an owner to the PyPI package. 😎 |
Thanks all!! The pre-release is out so we should be able to close this issue now. I opened #6307 as a follow-up to plan the 7.0 release. |
This describes the shortest path to get out a pre-release of Notebook v7 (currently called RetroLab).
There are still discussion around what we should do about git histories between jupyter/notebook and jupyterlab/retrolab (i.e. do we merge the two histories or not?). In the meantime, @bollwyvl mentioned changing the current
jupyter-notebook
entrypoint in notebook to retrolab might be a good place to start for the pre-release.I'd also like to suggest that we temporarily rename the jupyterlab/retrolab repository to jupyterlab/notebook-7 or something similar, since the name "retrolab" might add some confusion for users. It's officially notebook-7 now.
Here are the steps I propose (and we should discuss):
jupyter-notebook
entrypoint in jupyter/notebook to run retrolab.jupyter-classic
or something similar.Notebook 7 pre release steps
notebook_shim
as dependency tonbclassic
6.x
branchmain
(v7) (Draft PR to prepare for the move)Ping @tonyfast @bollwyvl @jtpio
The text was updated successfully, but these errors were encountered: