Skip to content

Doc release guide - #6466

Closed
tacaswell wants to merge 3 commits into
matplotlib:v1.5.1-docfrom
tacaswell:doc_release_guide
Closed

tacaswell wants to merge 3 commits into
matplotlib:v1.5.1-docfrom
tacaswell:doc_release_guide

Conversation

@tacaswell

Copy link
Copy Markdown
Member

Plan to fill this out as I go for the 1.5.2 release.


* remove font cache and tex cache from :file:`.matplotlib` and test
with and without cache on some example script
python unit/memleak_hawaii3.py

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we be running on Python 3 nowadays?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good point. I normally work in a conda env so python is python3 (and most of my machines are arch so python is also python3) so I forget that is not universally the case.

@jenshnielsen

Copy link
Copy Markdown
Member

Since we haven't merged #6044 of fixed #4205 perhaps it's useful to do something like

linkchecker build/html/index.html --check-extern

or using the build in linkchecer in Sphinx to check that our external links are not broken.



where `$TAG` is the tag of the last major release. This will generate
stats for all work done since that release.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

add note about installing requests + requests_cache

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants