Release Process - openstudiocoalition/OpenStudioApplication GitHub Wiki

The OpenStudio Application release process can be summarized in the following steps.

• Code Freeze
• Release Branch
• Release Candidates
• Final Release

Code Freeze

Code Freeze indicates that the code base is now frozen and there will not be any further modifications/changes to the code base. At this stage in the process, generally, only severe bug fixes reported by users during the release candidate process will be taken into consideration in terms of fixing for this release cycle.

Release Branch

Software managers will want to create a new branch associated with the release. This way developers can continue to develop in the main develop branch without interfering with the release branch.

git checkout -b v1.0.1

Release Candidates

Release candidates will be built from the release branch and marked in sequence.

OpenStudioApplication: NAME-MAJOR.MINOR.PATCH.SHA-OPERATING_SYSTEM.FILE_TYPE-RELEASE_CANDIDATE

e.g. OpenStudiApplication-1.0.0.b5c323884e-Darwin-rc1.dmg
e.g. OpenStudiApplication-1.0.0.b5c323884e-Darwin-rc2.dmg

Release candidates can either be distributed internally or externally depending on feedback desired. You can post on GitHub pre-release to indicate that this release is pre-release and not final. This process can last for 2 weeks until all feedback is given and cleared to go for release.

Final Release

Merge release branch to master and tag master branch with the release. Use this tag to post the official release in Github [release](GitHub pre-release)

git checkout master
git merge v2.9.1
git tag v2.9.1
git push origin master
git push origin --tags