Release Process

Changes made by Jadu should always be released independently to those made by yourselves or a third-party working on your behalf. The main reason for this is that it provides clear ownership of the release and therefore responsibility for resolving any issues that may arise.

Jadu recommends that you and/or third-parties working on your behalf should follow the recommended development process and coordinate releases according to your own schedule. If you have access to the Deployer tool, you do not need to inform Jadu when preparing or deploying a release.

When Jadu is preparing a release for you, there must be no new changes made to the dev branch while Jadu is conducting release testing. Jadu will request a change-freeze from yourselves during this period. The change-freeze only applies to the dev branch, changes can still be made to other branches. You must not create any new tags or start releases during this period.

Jadu will usually coordinate the change freeze period via a support ticket.

Hotfix Process

Where a release is already in progress and a change needs to be pushed to production urgently, Deployer provides support for a single hotfix branch - hotfixlive.

This branch should only be used to quickly rollout small fixes and not for new features or large complex changes. Create the hotfixlive branch from the tag currently deployed to production, then follow the usual process but treating hotfixlive as you would normally dev. When creating a new release in Deployer, the hotfixlive branch will be used in preference to dev.

Once deployed to live, the changes in hotfixlive must be merged back to dev and the hotfixlive branch deleted. The changes will then be incorporated into the next tag of the in-progress release.

If Jadu has a release in progress you must inform them before starting this hotfix process so that this can be accounted for in their work.