matplotlib / matplotlib/mpl-brochure-site
Syncing pushed branch and development branches....
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 6
- Forks
- 17
- Avg merge
- 4h 40m
- Merged PRs (30d)
- 3
Description
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.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the current branch and release conventions for the brochure site, along with how the doc site and mpl-sphinx-theme changes are synchronized. Define a branch arrangement that keeps the current page release-agnostic while allowing the 3.6 changes to be released later.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100