What Happens on Release Day
This page walks through a typical regular release from the perspective of shops and partners. No technical knowledge required.
Before release day
| Step | Who | What happens |
|---|---|---|
| 1 | Product team | Final list of changes is confirmed |
| 2 | QA team | Key flows are tested one last time |
| 3 | Support / agents | Release notes are shared with partners |
| 4 | Shop managers (optional) | Brief cashiers if cashier screens change |
tip
If you are a shop manager, you only need to act when release notes mention cashier, deposit, withdrawal, or new screens. Otherwise, no preparation is needed.
During release (usually low-traffic hours)
Release window opens (often evening or early morning, local time)
│
▼
System is updated on our servers
│
▼
Portals automatically use the new version
│
▼
Smoke checks — team verifies login, deposit, withdrawal still work
│
▼
Release is marked complete OR rolled back if a critical issue is found
What shops experience
- Short maintenance — in rare cases, portals may be unavailable for a few minutes
- No data loss — player balances and transaction history are preserved
- Same login — usernames and passwords do not change unless announced
What cashiers should do
- If already in an active shift, finish the shift normally unless support says otherwise
- After update, log out and log back in if screens look wrong (clears cached pages)
- Report anything unusual to the shop manager immediately
After release
| Activity | Purpose |
|---|---|
| Monitor support tickets | Catch issues shops report first |
| Hotfix if needed | Fix critical bugs without waiting for next cycle |
| Update this guide | Add or adjust flow docs if behavior changed |
If something goes wrong
| Situation | What to do |
|---|---|
| Cannot log in | Wait 5 minutes, try again; contact support if still failing |
| Balance looks wrong | Do not guess — note player ID, time, and amount; escalate to shop manager |
| Cashier screen changed unexpectedly | Check release notes; re-login; call support if flow is blocked |
| Withdrawal stuck | Shop manager checks approval queue |
We can roll back a release if a critical problem affects money or login for many users.
Hotfix (unplanned release)
A hotfix follows a shorter path:
- Problem is confirmed and prioritized
- Fix is tested on staging
- Deployed to production as soon as safe
- Short notice sent to affected roles
Hotfixes are reserved for serious issues — not minor UI preferences.
Related
- Release Notes Template — how we document each release
- Business Flows — processes that may change after an update