--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/8edb3ad3-c383-4c18-9595-81fb0732fa10n%40chromium.org.
Hey Henrik!I think the general outline of the plan makes sense, but the timelines seem too aggressive. As we've recently seen in the track stats removal, there can be a time difference between the point a developer puts in the work to opt-in for a deprecation trial and the point in which this work reaches users.
I think it would make sense to:* Add a deprecation warning in M113 and enable a Deprecation Trial. Set a tentative removal milestone for M119.* Start throwing an exception up to Beta in M114 to try and get people's attention* Broadly communicate this change is coming in multiple channels. DevRel folks may be able to help there. +Paul Kinlan and +Andre Bandarra for thoughts.* In parallel to the above, turn the usecounters into UKM, and try to see where most usage lies. (and try to understand if it's coming from libraries with longer deployment lifecycles)* Flip the switch (and be ready to revert) in M119I know this is a bit longer and more work than the plan you outlined, but given the few fire drills we had recently, it seems better to err on the cautious side.Also, do you know if more removals are planned on your side? It seems like it'd be better to "bundle" them so that library authors only have to "respin" their deployment once, rather than every few milestones.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAL5BFfVSMZDhsem91YtBc0R56M37SU4wi7s2bQcux4jjLkf9CA%40mail.gmail.com.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscribe@chromium.org.
OK, so deprecation warning in M113, throwing in Beta in M114 and throwing in Stable on M119. We can do that.
Under this less aggressive timeline, for how many more milestones would the Deprecation Trial span?
I do not have any more deprecations planned on my end and I think this is "standalone" enough (stats being rather specific) that in my opinion it should not be bundled together with anything else.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
On Mon, Feb 20, 2023 at 12:52 PM Henrik Boström <hb...@chromium.org> wrote:OK, so deprecation warning in M113, throwing in Beta in M114 and throwing in Stable on M119. We can do that.Awesome!Under this less aggressive timeline, for how many more milestones would the Deprecation Trial span?How much would be needed for people to schedule the work to make the switch?
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscribe@chromium.org.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAL5BFfXvoddJYizkHGzmavf6LLyqxY1VGLfZfW%3D%2BrmZBBHNq8Q%40mail.gmail.com.
LGTM3
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAARdPYfRn4nBRmfmvgJ8DFnmEZaCN_fGxqkEGsYK9z2ndyL1fQ%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAARdPYfRn4nBRmfmvgJ8DFnmEZaCN_fGxqkEGsYK9z2ndyL1fQ%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAARdPYfRn4nBRmfmvgJ8DFnmEZaCN_fGxqkEGsYK9z2ndyL1fQ%40mail.gmail.com.