Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Upgrade jupyter book to version 1.0.0 #379

Open
navarroc opened this issue Apr 25, 2024 · 1 comment
Open

Upgrade jupyter book to version 1.0.0 #379

navarroc opened this issue Apr 25, 2024 · 1 comment
Labels
3storypoints Between 7-15 hours of work, requiring back and forth communications to clarify a complex problem

Comments

@navarroc
Copy link
Member

The current version of jupyter book is 0.13.2 and there is now a 1.0 release. We should upgrade to the latest to pull in new features and fixes.
@navarroc navarroc added the 1storypoint Less than two hours of work, requiring only email communication label Apr 25, 2024
@navarroc navarroc added this to the 4.11.0 milestone Apr 25, 2024
@navarroc navarroc assigned navarroc and unassigned navarroc Apr 25, 2024
@navarroc navarroc added 2storypoints Between 2-6 hours of work, requiring email and/or a brief meeting 3storypoints Between 7-15 hours of work, requiring back and forth communications to clarify a complex problem and removed 1storypoint Less than two hours of work, requiring only email communication 2storypoints Between 2-6 hours of work, requiring email and/or a brief meeting labels Apr 25, 2024
@navarroc
Copy link
Member Author

From a quick test, there are some broken links from the introduction page to the testbed pages. There are likely some configurations that need to be updated.

@navarroc navarroc removed this from the 4.11.0 milestone Apr 25, 2024
@navarroc navarroc mentioned this issue Apr 25, 2024
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
3storypoints Between 7-15 hours of work, requiring back and forth communications to clarify a complex problem
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@navarroc