Skip to content

Conversation

jfbu
Copy link
Contributor

@jfbu jfbu commented Feb 24, 2021

Closes: #8925

It is not a critical or severe bug... it is a bug of a feature added at 3.5.0. I hesitated adding to CHANGES a 3.6.0 section and then making the PR on 3.x. In the end making the PR on 3.5.x but this and milestone can be changed of course. (it depends if there will be a 3.6.0 before next major release).

@jfbu jfbu added this to the 3.5.2 milestone Feb 24, 2021
@tk0miya
Copy link
Member

tk0miya commented Feb 24, 2021

The next release is 4.0. So please merge this into the master branch. (I'll create 4.x branch just before beta release)

@jfbu jfbu force-pushed the latex_maxunderfull branch from 016f21a to 40b145c Compare February 24, 2021 17:57
@jfbu jfbu changed the base branch from 3.5.x to master February 24, 2021 17:58
@jfbu jfbu modified the milestones: 3.5.2, 4.0.0 Feb 24, 2021
@jfbu
Copy link
Contributor Author

jfbu commented Feb 24, 2021

Merging into master

@jfbu jfbu merged commit 13341c7 into sphinx-doc:master Feb 24, 2021
@jfbu
Copy link
Contributor Author

jfbu commented Feb 24, 2021

Thanks for advice!

@jfbu jfbu deleted the latex_maxunderfull branch February 24, 2021 18:14
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jul 14, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants