🚨 Jupyter Book 2.0 planning and information: what to expect here #2281
Comments
choldgraf
changed the title
choldgraf
changed the title
choldgraf
changed the title
agoose77
pushed a commit
that referenced
this issue
Jan 6, 2025
This updates our banner to use a GitHub issue for ongoing information on the 2.0 switch (instead of using a blog post). My reasoning is that we can use that issue as the "source of truth" for external people that want to learn more about this transition, what to expect, where to learn more, etc. This might change over time so better to use a github issue than a blog post. Here's the issue: - #2281 Any objections from the @jupyter-book/core-team about this? I'm open to alternative suggestions!
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Context
We're currently focusing on developing the new version of Jupyter Book. This uses the new MyST Document Engine and involves a total re-write of Jupyter Book's back-end. We are prioritizing Jupyter Book 2.0 issues.
Where is Jupyter Book 2 developed?
Currently on the
nextbranch.How can I try it out?
There's an alpha release already available! Just do:
pip install -U jupyter-book>=2.0.0a0What are your development priorities?
We use this GitHub project for our priorities.
You can also follow this issue tracking a feature comparison between JB 1 and 2:
What will the release cadence be?
The major
alphaandbetalabels in our GitHub project correspond to promises about minimum features. Meanwhile, we will continually update the latest family of releases to pull in new upstream MyST engine fixes.Stay tuned for information about the release date for Jupyter Book 2 Beta.
Where can I learn more about Jupyter Book 2 and this process?
Moving forward we'll post updates on the new Jupyter Book blog. The Executable Books Blog also has some relevant historical posts. Here are a few links to help you get started:
What about Jupyter Book 1.0 issues?
Issues that aren't related to Jupyter Book 2.0 (and specifically on the project board above) are going to be de-prioritized. We'll do our best to fix bugs for 1.x issues, but cannot make any promises.
Sorry about this - but we've got very limited resources to maintain and develop this project! We welcome contributions that make progress towards the issues on the 2.0 project board
The text was updated successfully, but these errors were encountered: