Hi team,
We have entered release freeze period and to respect this process, there are several things that we need to highlight. In summary:
" All changes during 2018 EoY freeze are justifiable, well tested, safe to push, and have a rollback plan."

Hotfix and Data Changes

Hotfixes and data changes are reserved only for major incidents not for product features or improvement.

Major incident is main flow issue (search list, rooms, and reservations) that impacts > 20% customers.

Changes including:

Production data through #prod-change-review or troubleshoot-dbscript
AB test reconfiguration
Job enablement, such as but not limited to: hotel import - merging, review tagging.
Feature enablement through feature toggling.
Flow changes in Workflow Platform
Anything that changes production machine via tower, are not allowed during release freeze unless justfied and explicitly approved.

Changes in point 1 and 2 are reviewed and explicitly approved by domain owner through this board. Create an incident in ACT project with the following configuration:

label: adt2018-eoy-release (and adt2018-eoy-data-change for data changes)
component: DEMAND
affected services: <a must>
title for service hotfix: [HOTFIX] [YYYY-MM-DD] [Domain Name] Summary

example: [HOTFIX] [2018-12-12] [Search] Fix broken contract

title for data change: [DATA CHANGE] [YYYY-MM-DD] [Domain Name] Summary

example: [DATA CHANGE] [2018-12-12] [Content] Fix broken SEO data

description: comply the task description with this template.

Post the JIRA ID (ACT-XXXX) to #adt-release-sync and wait for domain owners approval.
After approved, test the changes on shared staging
Once it's done, ping respective domain owner to release your change. Stand by during the release in case rollback is needed.

In case of minor incident, the on-call engineer to announce him/herself as PIC in #accom-demand-release, #en-hotel-product.
In case incident worsen to major, escalate to domain owner. Alert the team to help put off the fire and investigating. Post the situation in #release-and-hotfix channel.
Create postmortem document for each incident, both minor and major.
Regular situation update is needed in important channels. Ask PMs to help update business metrics.

Shared staging is prioritized for production test for bug fix
As development is till going as usual, shared staging is still usable for product/services testing, but priority is still as mentioned in point 1.
In case shared staging is to be used for development test, do comply with the following rule:

Do not push the change directly onto service release branch, but instead create branch based on service release branch
Before deploying the changes to shared staging, mention domain owner alongside deploy announcement
Since shared staging is prioritized for bug fix, domain owner reserves right to override deployment of the shared staging

Search: aprsapi, hinv, aprso, aprsoi, aprsr, aprrank – @bobbypriambodo (+6289688157020)
Content: ne, aprcapi, aprnes, aprned, aprhd, aprhdjw, aprhdt, aprseo, aprseog, aprugp, aprugct – @febri (+6287737822967), @jogie (+6285945591391)
Booking & Ops: aprbapi, hb, aprops, aprpbo, aprbap, aprhbd, aprphd, aprwp – @aradea (+62816974455)
Other: acso – @jogie (+6285945591391), aprua – Riko (+6285218027249)
Scraping/COI: ascrape, acis, cis – @erik (+6281807885333)

Please read this carefully and let me know your concerns.

References:
Hotfix rule during EoY

ADT End of Year 2018 Release Freeze