Fv3config

-------------------

Major changes:
~~~~~~~~~~~~~~
- Added `--kubernetes` command-line flag to output a kubernetes config yaml to stdout

Minor changes:
~~~~~~~~~~~~~~
- Added the flag ``--mca btl_vader_single_copy_mechanism none to mpirun in fv3run`` to mpirun in fv3run
- Add ReadTheDocs configuration file
- Do not require output dir and fv3config to be remote in ``run_kubernetes``
- Fix bug when submitting k8s jobs with images that have an "_" in them

Breaking changes
~~~~~~~~~~~~~~~~
- Refactored run_kubernetes and run_docker to call run_native via a new API serializing
their args/kwargs as json strings. The
fv3config version in a docker image must be greater than or equal inside a
container to outside, or a silent error will occur.
- When output location is set to a local path, the job now runs in that output location instead of in a temporary directory which then gets copied. This is done both to reduce copying time for large jobs, and to improve visibility of model behavior while running.

------------------

- Began tagging version commits

------------------

- Initial pre-alpha release


Release Instructions
====================

Versions should take the form "v<major>.<minor>.patch". For example, "v0.3.0" is a valid
version, while "v1" is not and "0.3.0" is not.

1. Make sure all PRs are merged and tests pass.

2. Prepare a release branch with `git checkout -b release/<version>`.

3. Update the HISTORY.md, replacing the "latest" version heading with the new version.

4. Commit your changes so far to the release branch.

5. In the project root, run `bumpversion <major/minor/patch>`. This will create a new commit.

6. `git push -u origin release/<version>` and create a new pull request in Github.

7. When the pull request is merged to master, `git checkout master` and `git pull`,
followed by `git tag <version>`.

8. Run `git push origin --tags` to push all local tags to Github.

9. Run `make release` to push latest release to PyPI. Contact a core developer to get the
necessary API token.