Release Cycle

Github repository for Tellurium is largely comprised of two branches.

• develop branch is where all code should be committed.
• master branch is the default branch, and should only contain stable releases.

Other branches are encouraged to be created for developmental purposes, but should be removed once they are merged with develop branch. Check Coding Guidelines for more information on tellurium development.

Once it is ready to release, pull changes from develop branch to master branch, and create a Release targeting the master branch. Once this is done, binary wheels and installers should be built and uploaded. Tellurium has Travis CI which is configured to test the code whenever a commit is pushed. Naturally, release should be made to code that passes the tests.

Refer to Release Checklist for rundown of basic release workflow.