Skip to content

Bad Build Identification

Todd Volkert edited this page Feb 28, 2018 · 3 revisions

What makes for a bad build?

Bad builds are tagged dev releases that are affected by issues serious enough to keep us from releasing the build to a more stable channel (e.g. beta).

I found such an issue; how do I know which tagged dev releases are affected?

First, you need to identify which commit introduced the issue and which commit fixed the issue. Once you've done that, you can see which version tags apply to any given commit by viewing the commit in GitHub:

Bad commit

In this case, the breaking change affects builds as far back as v0.1.5. Once the fix commit has landed, you'll know which build picked up the fix.

What do I do once I know which dev releases are affected?

You update the Bad Builds page accordingly.

Flutter Wiki

Process

Framework repo

Engine repo

Infrastructure

Experimental features

Release Notes

Clone this wiki locally
You can’t perform that action at this time.