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.

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

page_source_suffix not in 1.3.5 #2278

Closed
ericholscher opened this issue Jan 29, 2016 · 13 comments
Closed

page_source_suffix not in 1.3.5 #2278

ericholscher opened this issue Jan 29, 2016 · 13 comments
Assignees
Milestone

Comments

@ericholscher
Copy link
Contributor

I added a a while ago adding page_source_suffix to HTML context, so you can tell if you're working on markdown or rst files. It isn't included in 1.3.5:

https://github.com/sphinx-doc/sphinx/blob/1.3.5/sphinx/builders/html.py#L427

It however has been in master for a long time:

https://github.com/sphinx-doc/sphinx/blob/master/sphinx/builders/html.py#L431

How is it not included in any of the releases?

@ericholscher
Copy link
Contributor Author

Seems like it isn't included in the stable branch, so it isn't being included in releases. How do I get this included in stable?

@ericholscher
Copy link
Contributor Author

This is the commit -- should be backwards compat, and included in releases, I think: 5f6503c

@tk0miya
Copy link
Member

tk0miya commented Jan 30, 2016

At this moment, the milestone for v1.4 is put on Feb. 8th.
So I think next major release is coming within a month (maybe beta releases are needed before proper one)

@shimizukawa Let us know about the release plan.

@shimizukawa
Copy link
Member

I'm going to release 1.4 alpha 1 around Feb 14th. I'll send my 1.4 release schedule to sphinx dev ML later.

@ericholscher
Copy link
Contributor Author

Great -- I guess my question is what I would have done differently to get that patch into the 1.3.x release? It's arguably a bug fix for the suffix support, as pages can't tell what markup they were rendered from.

@birkenfeld
Copy link
Member

I assume there was a PR made against the master branch. Bugfix releases are made from the stable branch.

@birkenfeld
Copy link
Member

That said, it is also our responsibility as maintainers to check whether a PR against master should go to stable instead.

@tk0miya
Copy link
Member

tk0miya commented Feb 8, 2016

+1 for stable.

Surely, page_source_suffix is a new template variable.
But it is a bug of multiple parsers support.
And it seems the commits is not a breaking change.

@ericholscher
Copy link
Contributor Author

👍 -- would love to see this get merged into a stable release as soon as possible. Should I open a PR against stable for this?

@birkenfeld
Copy link
Member

Yes, please. I don't know when @shimizukawa has planned the next 1.3.x release.

@shimizukawa
Copy link
Member

Ah, ok, I'll cherry-pick the commit by #1876 to avoid merge conflict.
BTW, I'm planning to release 1.3.6 around the end of this month (Feb, 2016).

shimizukawa added a commit that referenced this issue Feb 9, 2016
@shimizukawa
Copy link
Member

Now stable branch contains a 5f6503c change for page_source_suffix.

@shimizukawa shimizukawa added this to the 1.3.6 milestone Feb 9, 2016
@shimizukawa shimizukawa self-assigned this Feb 9, 2016
@ericholscher
Copy link
Contributor Author

Thanks!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants