Rc v0.3.2

[rstoneback]

Release Candidate for v0.3.2.

• Includes fixes to improve building with modern systems
• Compatible with pysat v3.0+
• Adds template documents for pulls, community documents, testing via GitHub Actions.
• Same CDF library version as last release.

I intend to have a follow up release that increments the CDF library version. For highest backwards compatibility I decided to release this minimum changes version first.

Note the current version online for PIP only works for Mac systems. This release is intended to bring pysatCDF back from the dead. Rehabilitation and such will follow to further bring pysatCDF up to full project standards. Progress has been made in this release to add template docs, code formatting improved, etc. pysatCDF passes all tests via pysatNASA and is approx. 60 times faster loading CDF files than pure python.

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation (no docs yet other than readme)
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules
• Add a note to CHANGELOG.md, summarizing the changes
• Update the version number
• Verify and update Zenodo information in .zenodo.json (Passes linter!, awaiting last confirmation of info)
• doc tests pass locally (pysatCDF doesn't have docs yet. Docs will be added along with multi-dimensional support)
• activate this branch on readthedocs (nothing to activate)
• Upload the test distribution to the testPyPi server (https://test.pypi.org/project/pysatCDF/0.3.2rc1/)
• Contacted developers and users about the future release
• Performed integration tests with downstream packages (I've run integration tests using pysatNASA optional_pysatcdf branch. Tests pass locally.)
• Create a wiki page with the release text (https://github.com/pysat/pysat/wiki/pysatCDF-v0.3.2-Release-Text)
• After approval, confirm all changes from the RC pull are listed in the wiki release text.

[rstoneback]

RC4 and RC5 via testpypi are compiling and passing pysatNASA tests on my local system. The relevant command for testpypi download.

python3 -m pip install --index-url https://test.pypi.org/simple/ pysatCDF==0.3.2rc5

[jklenzing]

This isn't formatting correctly for some reason.

[aburrell]

I am guessing this is a GitHub Markdown peculiarity 🦥

[aburrell]

Recommend using sections instead of boldface type.

[aburrell]

Same in other templates.

[rstoneback]

Thanks for the note. I copied the templates from somewhere in our ecosystem. I don't remember from which package now though. Will update.

[rstoneback]

pysatMadrigal and pysatSpaceWeather have

# Description
A clear and concise description of what the bug is, including a description
of what you expected the outcome to be.

while the others, pysat, Models, Missions, Seasons, and CDAAC have the same here. I'll copy from Madrigal/SpaceWeather. Went a bit out of strict ** to # replacement, but the SpaceWeather/Madrigal versions are two whole years newer than the other packages.

[aburrell]

Don't forget to add a date.

[rstoneback]

Thanks for the feedback!

[jklenzing]

Looks good!

[rstoneback]

Thanks everyone!