Skip to content
This repository was archived by the owner on Feb 25, 2025. It is now read-only.

Conversation

@chunhtai
Copy link
Contributor

@chunhtai chunhtai commented Nov 9, 2019

reland enum lifecycle

previous pr is reverted to unblock fuchsia roll

framework : flutter/flutter#44487
issue: flutter/flutter#39832

This reverts commit 8ebb318.
@xster
Copy link
Member

xster commented Nov 9, 2019

LGTM

@chunhtai chunhtai merged commit 1f1e2ba into flutter:master Nov 13, 2019
engine-flutter-autoroll added a commit to engine-flutter-autoroll/flutter that referenced this pull request Nov 13, 2019
engine-flutter-autoroll added a commit to engine-flutter-autoroll/flutter that referenced this pull request Nov 13, 2019
engine-flutter-autoroll added a commit to flutter/flutter that referenced this pull request Nov 13, 2019
[email protected]:flutter/engine.git/compare/b358dc58fbce...b6a0fb7

git log b358dc5..b6a0fb7 --no-merges --oneline
2019-11-13 [email protected] [web] Fix blendmode for images (flutter/engine#13809)
2019-11-13 [email protected] Roll buildroot to 0fec442. (flutter/engine#13837)
2019-11-13 [email protected] reland add lifecycle enum (flutter/engine#13767)


If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC [email protected] on the revert to ensure that a human
is aware of the problem.

To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md
@tvolkert
Copy link
Contributor

The removal of AppLifecycleState.suspending is a breaking change (and causing many failures inside Google when trying to roll this change in). Is there any way to make this a soft (multi-phase) transition, so that consumers can pick up the change without it being breaking, migrate their code, then follow-up with the second phase to cleanup?

/cc @Hixie as an FYI (example) since he's actively re-working our breaking change policy.

chunhtai added a commit to chunhtai/engine that referenced this pull request Nov 15, 2019
@Hixie
Copy link
Contributor

Hixie commented Dec 15, 2019

Where was the e-mail/documentation about this breaking change?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants