Official releases first
A product is considered released only when an official release exists. A main branch or internal plan is not a usable product.
Engineering practice
This page describes product release, testing, documentation, issue tracking, and acceptance practices. Customer information is published only with authorization.
Principles
A product is considered released only when an official release exists. A main branch or internal plan is not a usable product.
Versions, tests, interfaces, BOMs, and acceptance results remain traceable, with sources for important conclusions.
Test the highest-risk assumption before entering full development and larger investment.
Distinguish in-house work, coordinated resources, and external suppliers without presenting all supply chain capability as company-owned.
Track software, device, data, and pilot-production issues in one list until validation is complete.
Delivery includes deployment, documentation, and a maintenance path, not only a codebase.
Product practice
ZyHive publishes its source code and release chain. Ai Gliding is maintained through continuous public testing and version updates.
The project includes public source code, CI, cross-platform releases, installation, updates, and documented operating boundaries.
Public TestFlight BetaPublic testing covers product design, app and data engineering, release management, operations, security, privacy, and ongoing iteration.
Case policy
A published case requires customer approval and a clear description of the problem, scope, deliverables, and confirmed outcomes. Customer names, logos, and performance figures are not used without authorization.
Submit the project background, current stage, target outcome, and the main issue to be addressed.
Start a project