@reidbaker I'm leaning towards rejecting this as not being critical enough to warrant cherrypicking, unless you disagree. WDYT?

I'm sorry for interjecting, but I would argue this is an important fix that needed to be merge. It shows the responsibility and respect to other people's time.

I'm not familiar to Flutter's merging process myself, but I see this wouldn't hurt even though it's not critical.

It just so sad that for this past months, people are misguided when they shouldn't be since we already have this fix that hasn't landed in stable.

I apologize if I'm getting ahead of myself by making this request clearer. But I find the rejection reason nor whether there is any clear timeline of this fix to be merged to stable if this cherry pick request is going to be rejected hasn't made clear yet.

@christopherfujino I think the pick is safe enough, as to critical enough, I think migrations have the most value on the following release of the same type like stable to stable. I cant remember what the update patch schedule is but my answer is that if we were shipping a patch then I would lean towards taking this CP but I would not ask that we do a release solely for this CP.

@christopherfujino I think the pick is safe enough, as to critical enough, I think migrations have the most value on the following release of the same type like stable to stable. I cant remember what the update patch schedule is but my answer is that if we were shipping a patch then I would lean towards taking this CP but I would not ask that we do a release solely for this CP.

Thanks for the context

auto label is removed for flutter/flutter/149881, due to This PR has not met approval requirements for merging. The PR author is not a member of flutter-hackers and needs 1 more review(s) in order to merge this PR.

• Merge guidelines: A PR needs at least one approved review if the author is already part of flutter-hackers or two member reviews if the author is not a flutter-hacker before re-applying the autosubmit label. Reviewers: If you left a comment approving, please use the "approve" review action instead.