sphinx-doc / sphinx-doc/sphinx

9.1.1 Release plan

Open
#14,501 8 comments 6 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

type:task
Dominant language
Python
Stars
8k
Forks
2.6k
PR merge metrics
No merged PRs in 30d

Description

I saw the version was bumped to 9.1.1 so figured it would be a good idea to create an issue (seems fairly standard practice) to discuss what should go in it, etc.

Below are some PRs I thought would be worth adding, feel free to share your thoughts on other PRs etc.

  • 9.1.1 milestones (edit: given the list it should probable be renamed to 9.2.0)

Fix CI

Get the tests passing again

Priority

Stuff that seems important

Low impact PRs to merge

These are all approved, fairly simple, and seemingly low impact (verify yourself before merging)

Docs changes
Tests
Other

Autodoc

autodoc related changes

Docutils

Docutils related changes

Other

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with milestone 158 and review the listed pull requests, especially the CI fixes, priority item, and approved documentation and test queries. This issue is done when the release contents and target version are agreed, relevant PRs are selected, and the milestone reflects that decision.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
release
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.