Before the production track

Pre-release Stability Gate

Promoting a candidate because the office devices did not crash is how last month’s Xiaomi cluster returns on Monday morning. The gate is a short, named reading of the testing track.

Smartphone standing upright on a clean desk next to a plant

We do not run your test scripts. We read what the candidate already produces on the tracks you use: internal, closed, or open testing. If a signature from the last production version is still present, the note says hold and points at it.

Teams book a gate when a release includes an NDK bump, a new ads SDK, or a WebView-heavy screen. Those changes are where silent crash types tend to arrive.

Who this is for

Release owners who already have an internal candidate and want a second pair of eyes on vitals from internal, closed, or open testing tracks before promoting to production.

What you receive

A go / hold note tied to named clusters, not a vague “looks fine.” Hold means a cluster still matches a known fatal or ANR signature, or a new native crash has appeared.

Scope

One release candidate (one version code or a short version-code range) on testing tracks. Production users are out of scope unless you expand to a full audit.

Included

  • Reading of testing-track vitals and any crash reporter traffic for the candidate
  • Comparison against the previous production version’s top signatures
  • A one-page go / hold note with the clusters that drove the call
  • A thirty-minute call if the note is a hold

Not included

  • Signing the Play release for you
  • QA script execution or monkey-test farming
  • Fixing the hold items

How the work runs

  1. Candidate brief

    You tell us the version code, what changed, and which previous clusters you believe are closed.

  2. Track reading

    We watch the testing track for an agreed window — usually three to five days of real testers, not a single smoke pass.

  3. Note

    Go or hold, with signatures listed. Silence is not a go.

Preparation

Testing-track access, mapping for the candidate, and the list of clusters closed since the last production version.

Constraints

A gate with almost no testers cannot honestly say go. We will say the sample is too thin rather than invent calm.

Schedule a stability gate