Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Syncing pushed branch and development branches.... #54

Copy link
Copy link
@jklymak

Description

@jklymak
Issue body actions

We have substantive new changes in 3.6 for the doc site and the mpl-sphinx-theme that should show up here as well when 3.6 is released. However, 3.6 is not released, and this page is supposed to be release agnostic. That poses a bit of a problem. We probably should have two branches, one for the current page and its build, and one for the future page that can be released later? I don't want to unilaterally set that up as I'm not 100% sure what the conventions should be, but happy to try if no one else wants to orchestrate.

timhoffm

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      Morty Proxy This is a proxified and sanitized view of the page, visit original site.