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

Maintenance #1083

Closed
5 of 6 tasks
dopplershift opened this issue Jul 3, 2019 · 2 comments
Closed
5 of 6 tasks

Maintenance #1083

dopplershift opened this issue Jul 3, 2019 · 2 comments
Labels
Area: Infrastructure Pertains to project infrastructure (e.g. CI, linting) Type: Maintenance Updates and clean ups (but not wrong)
Milestone

Comments

@dopplershift
Copy link
Member

dopplershift commented Jul 3, 2019

A few todo list maintenance items I've been meaning to do before the next release:

  • Update Travis to use python 3.7-dev for "bleeding edge" builds
  • Update AUTHORS.txt for any new code contributors
  • Update year in LICENSE
  • Update .mailmap as needed to keep contributors unique
  • Remove any spurious warnings from tests/doc/example builds. I thought when building docs locally I was seeing our own deprecation warnings, which is silly.
  • Update CODEOWNERS to replace jrleeman with zbruick

This is a great way to find authors: git log --format='%aN %aE' | sort -u

I'm putting this here so I don't forget, but it's fair game if someone is exceedingly motivated. Just make sure you drop a note below if you happen to pick it up so we don't collide.

@dopplershift dopplershift added this to the 0.11 milestone Jul 3, 2019
@dopplershift dopplershift added Area: Infrastructure Pertains to project infrastructure (e.g. CI, linting) Type: Maintenance Updates and clean ups (but not wrong) labels Jul 3, 2019
@zbruick
Copy link
Contributor

zbruick commented Jul 5, 2019

Only item that remains is removal of spurious warnings.

@dopplershift
Copy link
Member Author

I don't see any spurious warnings left. There's one about gridding, which happens because we have gridding in the api docs. Then there are two I see from "viridis", which occur because we have an image of all our colortables in the docs. I think this is done.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: Infrastructure Pertains to project infrastructure (e.g. CI, linting) Type: Maintenance Updates and clean ups (but not wrong)
Projects
None yet
Development

No branches or pull requests

2 participants