Major/Minor Release (e.g. `v3.1.0`)

This page describes the process of making a release of OpenEXR and/or Imath.

...

All development happens in the master branch. PR's are merged into the master branch.
OpenEXR enforces a linear commit history. The GiHub repo allows squash merging and rebase merging but does not allow merge commits.
PR's are typically merged via "Squash and merge". This ensures that each PR ultimately corresponds to a single commit in the history. GitHub appends the PR number to the commit title upon squash, which makes this relationship easy to see: "Remove dead code in ImfB44Compressor.cpp (#1024)"
Each major and minor release goes into a branch named "RB", e.g. RB-3.0. Each release is a tag starting with lowercase 'v', e.g. v3.0.4. Patch releases are tags along the corresponding RB- branch.

Patch Release (e.g. `v3.0.4`)

...