Skip to main content

Release Notes Template

Use this template when writing public release notes. Copy the section below for each new release.

Template (copy for each release)​

# Release vX.Y.Z — [Date]

**Release type:** Regular | Hotfix | Soft release  
**Maintenance window:** [Date/time or "None expected"]  
**Who should read this:** Shop managers | Cashiers | Agents | All

---

## Summary (2–3 sentences)

[Plain-language overview of the most important changes.]

---

## What's new

- [Feature 1 — who benefits and what they can do now]
- [Feature 2]

## Improvements

- [Faster / clearer / easier — describe user-visible benefit]

## Fixes

- [Problem that users may have noticed — now resolved]

## Action required

- [ ] None — informational only
- [ ] Shop managers: [specific task, e.g. brief cashiers on new closing screen]
- [ ] Agents: [specific task]

## Known limitations

- [Anything not included yet or only in pilot]

## Support

Questions? Contact [support channel / your agent].

Example (fictional)​

Release v1.0.0 — June 11, 2026

Release type: Regular
Maintenance window: June 14, 11:00 PM – 11:15 PM (local)
Who should read this: Shop managers, Cashiers

Summary​

This release introduces cashier shift closing with blind count and improves withdrawal approval messages in the Shop portal.

What's new​

  • Cashiers can close a shift without seeing the expected cash total first (blind count)
  • Shop managers receive a notification when a shift has a cash discrepancy

Improvements​

  • Withdrawal approval screen shows clearer status labels (Pending / Approved / Rejected)

Fixes​

  • Fixed an issue where some cashiers could not see their assigned shift on login

Action required​

  • Shop managers: remind cashiers to complete blind count training before first close after release

Known limitations​

  • Handover between two cashiers on the same device is pilot-only in selected shops

Support​

Questions? Contact your agent or support@kioskgaming.com.

Writing tips​

  1. Lead with impact — start with what users will notice
  2. Name the role — "Cashiers can…", "Shop managers will see…"
  3. Avoid jargon — say "login screen" not "auth endpoint"
  4. Be honest about limits — soft release and known gaps build trust
  5. Keep it short — one page is enough for most releases