Release Freeze Guidelines

We plan releases of Empower after 2 sprints of development time (or about every 6 weeks), making exceptions holidays or extenuating circumstances and bugs.

Guidelines to follow during the release freeze period for repositories.

Repositories: empower-spark , empower-coreapi-service , empower-dataapi-service

1. The branch that will be frozen during release freeze period will be IN branch.
2. Developers can continue to merge their changes into development branch during code freeze period.
3. Any bug fixes that happen during the release freeze period will be tested on the dev environment, the respective PR's will be merged into development and IN branch.

Repository: empower-UI

Empower UI is global, it will have different set of rules during code freeze period to avoid impacting the ongoing
testing.

1. During code freeze the development branch and IN branch will be kept frozen.
2. The dev branch will be kept in sync with IN branch so that bugs that are fixed during release freeze can be merged to dev branch and IN branch
3. A separate release branch will be created to keep the code intact for upcoming releases and it can be merged into dev branch as code freeze is lifted for example branch name will be code-freeze-X-XX.

Repository: empower-frontdoor-service

Empower frontdoor repository is a global service and it will have different set of rules during code freeze period to avoid impacting the ongoing testing.