WRF Branch Flow

The following describes the flow for the various WRF branches, and tagged released code.

MAIN branch: contains the tagged releases
DEVELOP branch: for ongoing code development
RELEASE branches: These are created when it is agreed that a release is imminent, and from that point on, only bug fixes will be allowed to be added to this branch.

For a bug fix release, the branch should be created from the last official tagged release on the master branch (or the relevant release if the bug existed prior to the last release). For a major release, the development team will decide at what point they want to cut off development, and will create a release branch from that point.

Once the release branch is finalized, the release branch is merged onto master, tagged as a release, and then merged onto development so that those doing developmental work can incorporate the corrected code in their changes.