Downloading, Verifying, and Upgrading Product Versions

Product version records bind the installation package, target system, description, checksum, and release status together. Do not determine the version based on the filename alone.

flowchart LR
    A[Choose version and target OS] --> B[Download package]
    B --> C[Verify SHA-256 and signature]
    C --> D[Back up and upgrade]
    D --> E[Run production acceptance]

Selecting an Installation Package

Standard targets include:

Confirm the operating system, CPU architecture, whether it is self-contained, MediaServer/FFmpeg dependencies, and version notes. The business application and media dependencies must use compatible architectures.

Post-Download Verification

1. Download from the official version page of the licensing platform; do not use reprints from unknown sources.
2. Verify the four-segment product version and the target RID.
3. Calculate the SHA-256 checksum and compare it with the release record.
4. Check the VERSION, program information, and protection notes within the package.
5. Extract to a new directory; do not directly overwrite the currently running directory.

Stable versions should possess the complete set of planned supported RIDs. Once released, artifacts of the same version/RID must not be silently overwritten; any changes should result in a new version release.

How to Read Release Notes

Focus on the following:

• Database or configuration migrations;
• API contract and permission changes;
• Device protocol compatibility fixes;
• Fixed MediaServer versions and WebRTC capabilities;
• Known limitations and scenarios requiring re-acceptance;
• Rollback boundaries.

"Build successful" is not evidence of production readiness at the target site. The target OS, devices, browsers, NAT, and concurrency still require actual testing.

Upgrading

Execute according to Backup, Recovery, Upgrade, and Rollback. Before upgrading, save the current package, configuration, security directories, database, and checksums; perform regression testing with real devices in pre-production before deploying in batches.

Version Issue Feedback

Provide the product version, commit/release identifier, RID, component versions, package SHA-256, deployment method, and evidence of reproduction. Do not simply say "the latest version," as different environments may have cached or mirrored different artifacts.