Skip to content

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

Open
@jklymak

Description

@jklymak

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.

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