Version
The package needs a unique release identity.
CONTROLLED RELEASES
Downloads through controlled access.
Installation packages need version, platform and release context. No unverified or anonymous download links are shown.
Controlled access
Downloads
The customer portal is connected to TEA2. Only files and releases explicitly released to the customer become available after login.
Customer loginCONTROLLED RELEASES
Installation packages need version, platform and release context. No unverified or anonymous download links are shown.
Ask about access01
Windows DispatchWindows
Controlled02
Android / PoC clientAndroid
Controlled03
Release notesRelease
Controlled04
Checksums / integrityVerification
ControlledRELEASE CHANNEL
A download should trace back to a release.
Clients and installers should not circulate as anonymous files. Version, platform, release context and access must be clear before a customer receives a package.
Platform
Windows, Android/PoC or another target environment must be explicit.
Access
Customer material is distributed through a controlled channel.
01Release notes
Describe relevant changes, requirements and known limitations.
02Integrity
Checksums or equivalent verification can be tied to the concrete package.
03Lifecycle
It should be clear which builds are current or retired.
04Support
A fault report should identify exact version and platform.
Production downloads appear only when a concrete file has been released to the customer through TEA2 with the relevant release context.