RC version 0.2.0

[aburrell]

Description

Release candidate fulfilling v0.2.0 milestones.

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality or documentation)
• This change requires a documentation update

How Has This Been Tested?

Unit tests and examples

Test Configuration

• Operating system: OS X Big Sur
• Version number: Python 3.9
• Any details about your local setup that are relevant: RC branch of pysat

Checklist:

• [x] Update the version number
• [x] Verify and update Zenodo information in .zenodo.json
• [x] doc tests pass locally
• [x] activate this branch on readthedocs
• [x] Upload the test distribution to the testPyPi server: https://test.pypi.org/project/pysatMadrigal/0.2.0rc1/
• [x] Contacted developers and users about the future release
• [x] Performed integration tests with downstream packages (include list of these packages)
• [x] Create a wiki page with the release text: https://github.com/pysat/pysatMadrigal/wiki/v0.2.0
• [x] After approval, confirm all changes from the RC pull are listed in the wiki release text.
• [x] My code follows the style guidelines of this project
• [x] I have performed a self-review of my own code
• [x] I have linted the files updated in this pull request
• [x] I have commented my code, particularly in hard-to-understand areas
• [x] I have made corresponding changes to the documentation
• [x] My changes generate no new warnings
• [x] I have added tests that prove my fix is effective or that my feature works
• [x] New and existing unit tests pass locally with my changes
• [x] Any dependent changes have been merged and published in downstream modules
• [x] Add a note to CHANGELOG.md, summarizing the changes

If this is a release PR, replace the first item of the above checklist with the release checklist on the pysat wiki: https://github.com/pysat/pysat/wiki/Checklist-for-Release

[aburrell]

Poking @rstoneback and @JonathonMSmith for a review!

[rstoneback]

I've been trying to sort out where the reduction in testing coverage came from but coveralls has been giving me gateway errors for a couple days. Still is. Don't want to keep holding things up.

[aburrell]

@rstoneback it's because we can't download the LoS data (it's too big to handle through GH Actions). Coveralls has been stretched lately 😿