BFE Release Regulation

    BFE development follows git-flow, but makes some minor differences for github.

    • For the official bfe repository, developers should follow .

      • ‘master’ branch is the stable branch. Latest commit of the ‘master’ branch is unit-tested and regression-tested.

      • ‘develop’ branch is the development branch. Every commit of the ‘develop’ branch is unit-tested, but not regression-tested.

      • ‘release/vX.Y.Z’ branch is the temporary branch created for release. The code on this branch is undergoing regression testing.

    Release Regulation

    Follow the following procedures to release a new version:

    1. Create a new branch from the ‘develop’ branch with the name ‘release/vX.Y.Z’. For example,

    2. For the submission of this version, do the following:

      • Test the functional correctness of the version. If it fails, fixing all the bugs in the ‘release/vX.Y.Z’ branch, and return to the second step with patch number added by 1.

    3. Complete the writing of .

    4. Merge the ‘release/vX.Y.Z’ branch into the master branch, and delete the ‘release/vX.Y.Z’ branch. Merge ‘master’ branches into the ‘develop’ branch.

    5. Tag the latest commit of the master branch with ‘vX.Y.Z’

    Note:

    • When the ‘release/vX.Y.Z’ branch exists, merge the ‘bugfix’ branch into the ‘master’, ‘develop’ and ‘release/vX.Y.Z’ branches at the same time, if there are bugfix behaviors.