Development Guide

Some brief notes on development of KEPLER

Versioning

Starting with , the version number should be increased in the last digit for minor changes in code, e.g., bug fixes or changing of default values of parameters, updates to reaction rates, etc.

The second group should be increased whenever there is a change in the output format, or, optionally, for major changes.

See Semantic Versioning for more information about versioning.

Commit Workflow

Whenever you make changes, please document in History.rst.

You should first commit the change including updated documentation. Then build and push to web page the updated documentation as it contains the commit git hash tag.