Release Cycle
This page describes the rhythm of software updates — from planning to go-live.
Typical timeline
Plan → Build → Test → Release notes → Go live → Monitor
| Stage | What happens | Visible to shops? |
|---|---|---|
| Plan | Team decides what goes into the next release | No |
| Build | Features and fixes are developed | No |
| Test | QA checks flows (deposit, withdrawal, cashier, etc.) | No |
| Release notes | Plain-language summary is written | Yes — draft may be shared early |
| Go live | Update is deployed to production | Yes |
| Monitor | Team watches for issues after launch | Yes — if hotfix needed |
How often do we release?
| Cadence | Typical use |
|---|---|
| Every 2–4 weeks | Regular releases with features and fixes |
| As needed | Hotfixes for critical issues |
| By feature flag | Soft releases — new module enabled for pilot shops first |
Exact dates are shared in release notes before go-live when possible.
Environments (simple explanation)
We use separate copies of the system during development:
| Environment | Purpose | Who uses it |
|---|---|---|
| Staging | Final testing before public release | Internal team and pilot shops |
| Production | Live system used by all shops and players | Everyone |
You normally only interact with production. Pilot shops may be asked to try staging for early feedback.
Version numbers
Releases are labeled with a version, for example:
v1.0.0— initial production releasev1.0.1— small fix on top of v1.0.0
You do not need to track version numbers day to day. Release notes always say what changed in plain language.
Soft release vs full release
Some large features (e.g. Cashier Management) roll out in phases:
- Soft release — selected shops use the feature; feedback is collected
- Adjustments — fixes and training materials updated
- Full release — feature available to all eligible shops
During soft release, shops not in the pilot are not affected.
Next step
What Happens on Release Day — detailed walkthrough of release day