...
Major/Minor Release (e.g. v3.1.0
)
This page describes the process of making a release of OpenEXR and/or Imath.
Some important notes about the development process:
- 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)"
Patch Release (e.g. v3.0.4
)
This assumes that changes on the master branch need to be merged into the release branch, e.g. RB-3.0
.
...