On 5-Dec-2016 (monday), we will be cutting a release branch from develop as usual but this will be our last release branch for the year. There will be a normal backend push next week on 6 Dec 2016, which will be our last normal push for the year as well. Any further production changes after that (e.g.: hotfix, new product launch, etc) will have to be from the same release branch. Changes going into develop branch after next week release will not go to production until the end of the Freeze period, 10 Jan 2017.

We will also be tracking any production changes during the freeze period. If you need to push hotfix or any prod-related changes, please use the following process.

The PIC makes proposal using Asana for hotfix
The PIC asks an approval from Team Lead
Team Lead approves by commenting on the Asana
The PIC pushes the update to the release branch (special release branch will be created)
The PIC cherry-picks it to develop (this is necessary because we will not be merging hotfix in release branch back to develop until 10 Jan 2017)
The PIC pushes the update to staging06
The PIC runs test on staging06 (run your unit test/ manual test for your team)
The PIC releases to Production
The PIC marks the Asana completed

Notes for Team Lead:
Please make sure that the hotfix is justifiable, well tested and safe to push. If changes can wait until 10 Jan, please postpone the change.

If you need additional information, please feel free to contact @kevinwibowo.

EoY Release Procedure