Understanding Draft, Ready, and Published Statuses

HyperRelease structures every release around three simple statuses. That simplicity is deliberate: too much granularity drowns information, too little makes it unusable. Here is what Draft, Ready, and Published mean in release coordination.

Draft: work in progress

A release or platform in Draft is being prepared. Code may still be changing, store content is not final, the checklist is incomplete. It is the default state when you create a new version.

Ready: validated for publication

Ready means the team considers the platform ready to publish or submit for store review. Tests have passed, assets are in place, content is proofread. The ball is in the court of publication or App Review.

Published: live for users

Published confirms the version is accessible to your users on that platform. The cycle for that surface is complete. HyperRelease keeps the history for reference and feeds the public changelog when enabled.

In summary

These three statuses are enough for most teams to coordinate without ambiguity. HyperRelease applies them per platform, because a release is never truly "done" until every surface is Published.