I thought this text was relatively neutral (just informing them that it exists and that they might want to use it), but I don't feel strongly about exactly what we say. What did you have in mind?

I can see this being too successful and converting 80% of stable users to the beta channel, because it might be perceived as a recommendation. (Or, tongue in cheek: "Real experienced developers use the beta channel"!)

I wonder about instead using a message on the master/main channel that says something like, "This channel is designed for those contributing code to the Flutter project. Alternatively, you may want to consider the beta channel, which is both regularly updated and sufficiently tested for production usage."?

I mean, if it's "too successful" we can always just remove the message! Since we have no particular targets I'm not especially concerned.

In #126936 I'm adding channel descriptions for flutter channel which should push people away from master/main.

I'm not sure exactly when you're suggesting showing the message you suggest. Can you elaborate?

I'm suggesting a commit very like the one that you're proposing here, but targeting master channel users when they run flutter upgrade, instead of stable users.

Our recent data showed that master channel usage has grown from ~1% to ~4%, whereas beta channel usage has remained flat at ~1%. If half of those master channel users converted to beta, we'd already be in a better place.

Seems reasonable, let me whip up a new PR.

Submitted a version of this for upgrading on "master" as #127146

I'd suggest we don't merge this one for now, and see how the other PR works out first. If we keep this, I'd probably simplify the text to something like, "For information on other Flutter release channels, visit foo.bar"

Roger.