Release standards

Every Saleculator release should be easy to trust and support.

Customers, resellers, and hardware vendors should always find clear downloads, plain release notes, upgrade guidance, and support information for the version they are installing.

Customer downloads

Use clear versioned installer names, visible release notes, and a direct download path for customers who want to try Saleculator immediately.

Partner packages

Keep a separate vendor package for reseller rollouts, hardware preparation, Linux counters, and Raspberry Pi class POS appliances.

Release notes

Write release notes in business language: what improved, which issues were fixed, who should upgrade, and what customers should test before live use.

Upgrade safety

Every upgrade page should remind customers to back up, test one counter first, confirm receipt printing, and verify reports before updating every machine.

Support readiness

Each release should help support teams identify the version, package, operating system, device list, and customer setup mode quickly.

Legacy continuity

Keep existing update URLs available for older Saleculator installations so current customers are not cut off during the relaunch.

Before publishing

Customer and partner readiness

After publishing

Public confidence checks