-
Notifications
You must be signed in to change notification settings - Fork 5
Update issue templates for the jupyter/notebook
repo
#7
Comments
jupyter/notebook
jupyter/notebook
repo
Oh yeah, this definitely needs updating. Let's aim to update this in the PR that merges retrolab into notebook repo. |
This is even worse now because there is literally no way from the "choose" page to open a new issue. |
Just updated the |
Wasn't it on purpose, so we get the issue templates setup first to not confuse folks with the v6 to v7 transition? |
Pinging other regular attendees of the Notebook meeting for help with this, thanks! |
Current state is the following. Linking to jupyterlab could be changed now that main branch target v7. This will for sure evolve based on yesterday discussion (nbclassic..)
|
we discussed this issue in the notebook meeting today. now that we are releasing v7 it will be important to update these new issue submissions so they are easier for people to understand and submit feedback. cc @RRosio |
Closing as fixed by jupyter/notebook#6939, thanks @RRosio! |
Right now opening a new issue on the
jupyter/notebook
repo gives a very limited set of choices: https://github.com/jupyter/notebook/issues/new/chooseThis is because the classic notebook v6 has been in maintenance mode for a while now.
As we move forward with the plan for Notebook v7, we should consider updating these templates accordingly, since we'll also be using the notebook repo to develop Notebook v7 (RetroLab) and track issues.
The new issue templates should make it clear to the users there is a new stream of work happening in the repo for Notebook v7. And Notebook v6 tracked in the
6.x
branch.cc @Zsailer @tonyfast @afshin since this was discussed at some of the weekly meetings: #5
The text was updated successfully, but these errors were encountered: