fperez
commented
8 years ago Very good point! Jamie, do you want to take a stab at this one? We can work on the review cycle together
On Fri, Apr 29, 2016, 05:53 Peter Parente notifications@github.com wrote:
At the dev meeting, we had a discussion about the transition from the existing notebook UI / extension API to the new Jupyter Lab UI / API that yielded a nice sequence of phases with criteria for transitioning among them on the board. It's mostly captured in the hackpad under Tuesday, though the criteria for transitioning went missing. (I took a stab below at adding them back in from memory.)
I don't think these phases wound up in the roadmap. I really think they should to help the community understand how Jupyter Lab will come into play.
@fperez https://github.com/fperez @JamiesHQ https://github.com/JamiesHQ I didn't submit a PR because I think you're actively editing the roadmap. If you'd like me to, just let me know.
@ellisonbg https://github.com/ellisonbg @sccolbert https://github.com/sccolbert If I misremembered the criteria, please
correct!
From https://jupyter.hackpad.com/Spring-2016-Dev-Meeting-h0y1TIAWxz1
- Phase 1:
- A series of major releases starting with 5.0 that will have the existing notebook pages as the main UI with a JupyterLab button that takes people to the new JupyterLab page
- These releases may have new features in the existing notebook pages, some API changes, focus on transitioning to JupyerLab.
- These releases will have bug fixes and new features in JupyterLab designed to get JupyterLab to Phase 2.
- During this phase, we will continue to work on porting nbextensions to JupyterLab and building the bridge layers.
- Explicit that people can request help for porting extensions.
- Criteria for transition to phase 2:
- Jupyter Lab has all the primary functionality of the classic notebook interface.
- Jupyter Lab offers some interesting features beyond the classic interface.
- At least some important, popular extensions are ported / bridged to Jupyter Lab.
- Documentation and examples exist for creating Jupyter Lab plug-ins.
- Phase 2:
- A series of major releases that will have JupyterLab as the main UI and the old notebook is available as a button
- At this point, we start to discourage the development of new features in the existing notebook.
- Criteria for transition to phase 3:
- No major development or use of the classic UI.
- Phase 3:
- Starting with the z.0 major release. will remove the existing notebook pages.
- Maybe offer the existing notebook as a server extension.
— You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub https://github.com/jupyter/roadmap/issues/20
JamiesHQ
parente
At the dev meeting, we had a discussion about the transition from the existing notebook UI / extension API to the new Jupyter Lab UI / API that yielded a nice sequence of phases with criteria for transitioning among them on the board. It's mostly captured in the hackpad under Tuesday, though the criteria for transitioning went missing. (I took a stab below at adding them back in from memory.)
I don't think these phases wound up in the roadmap. I really think they should to help the community understand how Jupyter Lab will come into play.
@fperez @JamiesHQ I didn't submit a PR because I think you're actively editing the roadmap. If you'd like me to, just let me know.
@ellisonbg @sccolbert If I misremembered the criteria, please correct!
From https://jupyter.hackpad.com/Spring-2016-Dev-Meeting-h0y1TIAWxz1