Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Do 0.10.0 release (final release for Jlab 1.x) and then upgrade to Jlab 2.0
See original GitHub issueJupyterlab 2.0 marches towards release. The api is now (theoretically) locked down, so I think that the time is right to think about upgrading jupyterlab-git to be Jupyterlab 2.0 compatible.
I think we should cut a final Jupyterlab 1.x compatible release (which will be v0.10.0) of jupyterlab-git. Following that, we should then upgrade the master branch to be compatible with Jlab 2.0.
I’ve volunteered to help out with the Jlab 2.0 migration guide for extension devs. I’d like to do the 2.0 upgrades myself, and use my experiences as content for the guide. I’m also willing to handle the release, but if any of the other active maintainers (cough @fcollonval cough @kgryte) want to volunteer to do the release, I’d be happy to help get you the needed permissions on pypi and npmjs.
Does that sound like a reasonable plan to you guys?
Issue Analytics
- State:
- Created 4 years ago
- Reactions:5
- Comments:11 (11 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
My only further thought is that it would be good to figure out what needs to be in that final JLab 1.x compatible release. There are a few outstanding bugs and features which should likely be resolved before we focus exclusively on JLab 2.0.
@fcollonval, you should now have publish rights on npm.