Hi - any movements on this PR?

@Leedehai No, per the comment in the PR description:

Do not land until that feature is on stable.

@gaaclarke : Did this hit stable yet?

@gaaclarke : Did this hit stable yet?

no, siree

@gaaclarke, I see that issue flutter/flutter#13937 is closed because it has been fixed on master. Do you know when it will hit stable? I see a few possible approaches:

• We add a note to the text that this is fixed on master and then remove when it hits stable
• We add a note that it will be stable in release 3.3.8 (or whatever)
• We leave this PR as is until it does actually hit stable

I'm not a fan of lingering PRs, but sometimes it's just the way it is.

@gaaclarke, I see that issue flutter/flutter#13937 is closed because it has been fixed on master. Do you know when it will hit stable?

I have a rough idea. I don't know if publicly we've promised a date for the next stable release. It may be later than we were originally expecting. It will be the next stable release though.

I see a few possible approaches:

• We add a note to the text that this is fixed on master and then remove when it hits stable
• We add a note that it will be stable in release 3.3.8 (or whatever)
• We leave this PR as is until it does actually hit stable

I'm not a fan of lingering PRs, but sometimes it's just the way it is.

It isn't bothering me beyond the stress of making sure it doesn't get forgotten. Any of those sounds fine to me, just let me know what works for you. I already am in this predicament because of the medium article I'm sitting on anyways.

ok, I'll leave this for now. But I'm happy to review your article, @gaaclarke!

ok, I'll leave this for now. But I'm happy to review your article, @gaaclarke!

Thanks shams, it's the one you already reviewed, not a new one =)

closing