Page MenuHomePhabricator
Create Task
Maniphest T405177

Revise Tone: Instrumentation
Open, HighPublic3 Estimated Story Points
Actions

Description

User story & summary:

As the Growth team, I want instrumentation set up for the Revise Tone task so that we can measure how newcomers engage with it and evaluate its impact on new editors.

Details:

  • Implement instrumentation to track user interactions with the Revise Tone Structured Task. Events should capture entry, task interaction, and completion flows to support evaluation of feature adoption and effectiveness.
  • Partner with product Analytics to decide on instrumentation details: T397247: Measurement Plan: Revise Tone Structured Task (WE1.1, FY25-26)
Acceptance criteria:
  • Implement instrumentation necessary to support the Revise Tone Measurement Plan / Revise Tone Instrumentation Specs
    • The following things should be instrumented with xLab/Test-Kitchen:
      • clicks (+if time allows impressions) on a Revise Tone task on the Homepage
      • clicks (+if time allows impressions) on the save buttons (both in VE directly and in the edit-comment dialog) while in a Revise Tone Task
      • clicks on the "Revise" button
      • clicks/submits of a declined Revise Tone Edit Check with the respective reason
  • We collect neither IP addresses nor Browser User Agents
NOTE: This task excludes instrumentation needed for the onboarding quiz. That will be covered in: T406252: 🧑‍💻 Instrument the Revise Tone Onboarding Quiz

Details

Related Changes in Gerrit:
SubjectRepoBranchLines +/-
instrumentation(ReviseTone): fix stream for edits and refine exposuremediawiki/extensions/GrowthExperimentsmaster+43 -69
instrumentation(ReviseTone): fix stream for edits and refine exposuremediawiki/extensions/GrowthExperimentswmf/1.46.0-wmf.4+43 -69
instrumentation(ReviseTone): fix stream for edits and refine exposuremediawiki/extensions/GrowthExperimentsmaster+24 -68
anlytics(ReviseTone): use ReviseToneExperimentInteractionLogger instead of experimentmediawiki/extensions/GrowthExperimentsmaster+6 -40
[beta] GrowthExperiments: increase log level to debugoperations/mediawiki-configmaster+1 -1
instrumentation(ReviseTone): manually collect revision and namespacemediawiki/extensions/GrowthExperimentsmaster+4 -2
EventStreamConfig: drop revision and namespace id from contributors.experimentsoperations/mediawiki-configmaster+0 -2
ReviseToneExperimentEditIngress: add debug statementsmediawiki/extensions/GrowthExperimentsmaster+24 -2
fix(ReviseToneExperimentInteractionLogger): prevent breaking homepage for unsampled usersmediawiki/extensions/GrowthExperimentswmf/1.46.0-wmf.3+7 -1
analytics(ReviseTone): log an edit_save event for users in experimentmediawiki/extensions/GrowthExperimentsmaster+45 -0
fix(ReviseToneExperimentInteractionLogger): prevent breaking homepage for unsampled usersmediawiki/extensions/GrowthExperimentsmaster+7 -1
EventStreamConfig: add stream for Growth and Editing team edit ratesoperations/mediawiki-configmaster+34 -0
analytics(ReviseTone): add experiment instrumentationmediawiki/extensions/GrowthExperimentsmaster+38 -4
analytics(ReviseTone): add configured experiment instrument clientsmediawiki/extensions/GrowthExperimentsmaster+98 -0
Show related patches Customize query in gerrit

Related Objects
Search...

Event Timeline

There are a very large number of changes, so older changes are hidden. Show Older Changes
KStoller-WMF triaged this task as Medium priority.Sep 21 2025, 10:53 PM
KStoller-WMF updated the task description. (Show Details)
KStoller-WMF moved this task from Inbox to Blocked on the Growth-Team board.

(Moving to blocked for now, as we will need to start T397247: Measurement Plan: Revise Tone Structured Task (WE1.1, FY25-26) before engineers can start instrumentation.)

KStoller-WMF moved this task from Blocked to Backlog on the Growth-Team board.Oct 2 2025, 8:37 PM
Michael moved this task from Backlog to Needed for Q2 Release on the Revise-Tone-Structured-Task board.Oct 10 2025, 7:11 PM
Michael mentioned this in T407031: Revise Tone: Performance metrics are collected.Oct 10 2025, 7:24 PM
KStoller-WMF moved this task from Backlog to Current Quarter Backlog on the Growth-Team board.Oct 21 2025, 12:14 AM
KStoller-WMF renamed this task from Revise Tone: Instrumentation to Revise Tone: Instrumentation.Nov 2 2025, 9:07 PM
KStoller-WMF raised the priority of this task from Medium to High.
KStoller-WMF updated the task description. (Show Details)
KStoller-WMF updated the task description. (Show Details)Nov 3 2025, 5:06 PM
Michael updated the task description. (Show Details)Nov 3 2025, 5:09 PM
KStoller-WMF set the point value for this task to 3.Nov 3 2025, 5:15 PM
Urbanecm_WMF subscribed.Nov 3 2025, 5:20 PM

FWIW, the homepagevisit and homepagemodule schemas (and consequently, newcomertasks, which is linked to the previous one) currently collect client IP address. This is something we opted into (a long time ago). In addition to this, all schemas log the User-Agent. Both User-Agent and IP address are considered personal information by our privacy policy. Since we also collect unhashed user ID, we would very likely fail the last low risk criteria, which would make the collecting a Medium risk => requiring L3SC approval.

@Michael said we do not need neither UA nor IP address, so it might make sense to remove that instead, but currently, this is something we need to work against.

Michael mentioned this in T406252: 🧑‍💻 Instrument the Revise Tone Onboarding Quiz.Nov 3 2025, 5:29 PM
Michael updated the task description. (Show Details)Nov 3 2025, 7:16 PM
KStoller-WMF assigned this task to Sgs.Nov 4 2025, 4:56 PM
KStoller-WMF moved this task from Current Quarter Backlog to Up Next (estimated tasks) on the Growth-Team board.
KStoller-WMF moved this task from Up Next (estimated tasks) to FY2025-26 Q2 Sprint 3 on the Growth-Team board.
KStoller-WMF edited projects, added Growth-Team (FY2025-26 Q2 Sprint 3); removed Growth-Team.
Sgs moved this task from Incoming to Doing on the Growth-Team (FY2025-26 Q2 Sprint 3) board.Thu, Nov 6, 4:35 PM
Sgs added a comment.Mon, Nov 10, 5:25 PM
In T405177#11336794, @Urbanecm_WMF wrote:

FWIW, the homepagevisit and homepagemodule schemas (and consequently, newcomertasks, which is linked to the previous one) currently collect client IP address. This is something we opted into (a long time ago). In addition to this, all schemas log the User-Agent. Both User-Agent and IP address are considered personal information by our privacy policy. Since we also collect unhashed user ID, we would very likely fail the last low risk criteria, which would make the collecting a Medium risk => requiring L3SC approval.

@Michael said we do not need neither UA nor IP address, so it might make sense to remove that instead, but currently, this is something we need to work against.

As I understand the comment it is assuming that we would be using these three schemas (homepagevisit, homepagemodule,newcomertasks), but it was requested from @Iflorez to use Test Kitchen as much as possible. So my idea was to use web base schema instead to ensure we remain on a low risk tier. Does this make sense?

gerritbot added a comment.Tue, Nov 11, 1:47 PM

Change #1203812 had a related patch set uploaded (by Sergio Gimeno; author: Sergio Gimeno):

[operations/mediawiki-config@master] EventStramConfig: add stream for Growth's revise tone experiment

https://gerrit.wikimedia.org/r/1203812

gerritbot added a project: Patch-For-Review.Tue, Nov 11, 1:47 PM
Sgs added a comment.Wed, Nov 12, 3:21 PM

@Iflorez, I have some questions about the instrumentation spec:

  • Constructive edit rate: the spec for this event says edit (made on mobile web within a user's first 24 hours [where the edit is not reverted within 48 hrs]), I am assuming this restrictions will be ensured in post analysis rather than by the instrumentation itself, because I'm seeing time criteria applied in the constructive edit rate metric query, for instance INTERVAL 48h, is this assumption correct?
  • Is the assumption above also correct for the rest of metrics that use the edit_save event data? Or said differently, the edit_save event needs to be recorded for all kinds of edits performed by users in the experiment sample (both groups) and during the experiment. Regardless of their account age, edit count, etc.
  • The task rejection rate requires to record a page-visited event, however the task completion rate requires a Click on the RT card itself which launches the onboarding event. Is this intentional? Shouldn't the denominator for these two rates be the same one: clicks on the RT card? If not, could you clarify which "page visited" are we supposed to record?

`

Iflorez added a comment.Thu, Nov 13, 1:17 AM

Hola @Sgs:

  • Constructive edit rate: the spec for this event says edit (made on mobile web within a user's first 24 hours [where the edit is not reverted within 48 hrs]), I am assuming this restrictions will be ensured in post analysis rather than by the instrumentation itself, because I'm seeing time criteria applied in the constructive edit rate metric query, for instance INTERVAL 48h, is this assumption correct?

Yes, the Constructive Edit rate metric will be calculated in the analysis/query. In analysis we can pull all edit_save events and determine whether an edit qualifies as a constructive edit, based on timing rules and revert status. To calculate Constructive Edit rate we need interaction data including edit_saved.

  • Is the assumption above also correct for the rest of metrics that use the edit_save event data? Or said differently, the edit_save event needs to be recorded for all kinds of edits performed by users in the experiment sample (both groups) and during the experiment. Regardless of their account age, edit count, etc.

Yes; you can see the constructive_edit_rate calculation and how it's using edit_save.

  • The task rejection rate requires to record a page-visited event, however the task completion rate requires a Click on the RT card itself which launches the onboarding event. Is this intentional? Shouldn't the denominator for these two rates be the same one: clicks on the RT card? If not, could you clarify which "page visited" are we supposed to record?

Indeed these are defined differently/separately and are not mirror concepts. Task Rejection rate captures a click on decline from the edit-check-1 view (the name used in the design spec) and Task Completion rate captures a wider start ---> end trajectory. cc @KStoller-WMF

gerritbot added a comment.Thu, Nov 13, 12:16 PM

Change #1204840 had a related patch set uploaded (by Sergio Gimeno; author: Sergio Gimeno):

[mediawiki/extensions/GrowthExperiments@master] WIP: revise tone instrumentation

https://gerrit.wikimedia.org/r/1204840

KStoller-WMF updated the task description. (Show Details)Thu, Nov 13, 6:26 PM
gerritbot added a comment.Fri, Nov 14, 3:17 PM

Change #1205179 had a related patch set uploaded (by Sergio Gimeno; author: Sergio Gimeno):

[mediawiki/extensions/GrowthExperiments@master] analytics(ReviseTone): add configured experiment instrument clients

https://gerrit.wikimedia.org/r/1205179

gerritbot added a comment.Fri, Nov 14, 4:29 PM

Change #1205179 merged by jenkins-bot:

[mediawiki/extensions/GrowthExperiments@master] analytics(ReviseTone): add configured experiment instrument clients

https://gerrit.wikimedia.org/r/1205179

gerritbot added a comment.Fri, Nov 14, 4:37 PM

Change #1205188 had a related patch set uploaded (by Sergio Gimeno; author: Sergio Gimeno):

[mediawiki/extensions/GrowthExperiments@master] analytics(ReviseTone): log an edit_save event for users in experiment

https://gerrit.wikimedia.org/r/1205188

ReleaseTaggerBot added a project: MW-1.46-notes (1.46.0-wmf.3; 2025-11-19).Fri, Nov 14, 5:00 PM
Sgs moved this task from Doing to Code Review on the Growth-Team (FY2025-26 Q2 Sprint 3) board.Mon, Nov 17, 12:04 PM
Sgs added a comment.Mon, Nov 17, 4:08 PM
In T405177#11369242, @Iflorez wrote:

Hola @Sgs:

  • Constructive edit rate: the spec for this event says edit (made on mobile web within a user's first 24 hours [where the edit is not reverted within 48 hrs]), I am assuming this restrictions will be ensured in post analysis rather than by the instrumentation itself, because I'm seeing time criteria applied in the constructive edit rate metric query, for instance INTERVAL 48h, is this assumption correct?

Yes, the Constructive Edit rate metric will be calculated in the analysis/query. In analysis we can pull all edit_save events and determine whether an edit qualifies as a constructive edit, based on timing rules and revert status. To calculate Constructive Edit rate we need interaction data including edit_saved.

Is this also the case to determine if an edit was a revise-toneone or not? I cannot see any revise-tone tag in the metric catalog queries so I'm wondering if we need this information somewhere in the instrumentation or it will only be necessary on manual analysis instead of automated and that's why I cannot find it in the queries.

gerritbot added a comment.Mon, Nov 17, 7:49 PM

Change #1204840 merged by jenkins-bot:

[mediawiki/extensions/GrowthExperiments@master] analytics(ReviseTone): add experiment instrumentation

https://gerrit.wikimedia.org/r/1204840

Iflorez added a comment.EditedMon, Nov 17, 11:00 PM
In T405177#11379529, @Sgs wrote:
In T405177#11369242, @Iflorez wrote:

Hola @Sgs:

  • Constructive edit rate: the spec for this event says edit (made on mobile web within a user's first 24 hours [where the edit is not reverted within 48 hrs]), I am assuming this restrictions will be ensured in post analysis rather than by the instrumentation itself, because I'm seeing time criteria applied in the constructive edit rate metric query, for instance INTERVAL 48h, is this assumption correct?

Yes, the Constructive Edit rate metric will be calculated in the analysis/query. In analysis we can pull all edit_save events and determine whether an edit qualifies as a constructive edit, based on timing rules and revert status. To calculate Constructive Edit rate we need interaction data including edit_saved.

Is this also the case to determine if an edit was a revise-toneone or not? I cannot see any revise-tone tag in the metric catalog queries so I'm wondering if we need this information somewhere in the instrumentation or it will only be necessary on manual analysis instead of automated and that's why I cannot find it in the queries.

Short answer: no, we do not need to add revise-tone tag info to the instrumentation build out. That information will only be utilized in the manual analysis.

In more detail: To determine if an edit was a revise-tone edit we'll perform a manual analysis with data pulled from the Test Kitchen table on the event database (using revision_id, wiki, namespace id, and revision date range information) and the event.mediawiki_revision_tags_change table (using database, rev_timestamp, rev_id, tags). See cells F14 to F16 in the instrumentation specification.

Iflorez added a comment.Mon, Nov 17, 11:49 PM

Adding this quick update for tracking for future reference:

See the latest on the new Test Kitchen stream and stream naming discussion related to https://gerrit.wikimedia.org/r/c/operations/mediawiki-config/+/1203812

gerritbot added a comment.Tue, Nov 18, 2:30 PM

Change #1203812 merged by jenkins-bot:

[operations/mediawiki-config@master] EventStreamConfig: add stream for Growth and Editing team edit rates

https://gerrit.wikimedia.org/r/1203812

Stashbot added a comment.Tue, Nov 18, 2:30 PM

Mentioned in SAL (#wikimedia-operations) [2025-11-18T14:30:52Z] <sgimeno@deploy2002> Started scap sync-world: Backport for [[gerrit:1203812|EventStreamConfig: add stream for Growth and Editing team edit rates (T405177)]]

Stashbot added a comment.Tue, Nov 18, 2:36 PM

Mentioned in SAL (#wikimedia-operations) [2025-11-18T14:36:00Z] <sgimeno@deploy2002> sgimeno: Backport for [[gerrit:1203812|EventStreamConfig: add stream for Growth and Editing team edit rates (T405177)]] synced to the testservers (see https://wikitech.wikimedia.org/wiki/Mwdebug). Changes can now be verified there.

Stashbot added a comment.Tue, Nov 18, 2:40 PM

Mentioned in SAL (#wikimedia-operations) [2025-11-18T14:40:57Z] <sgimeno@deploy2002> Finished scap sync-world: Backport for [[gerrit:1203812|EventStreamConfig: add stream for Growth and Editing team edit rates (T405177)]] (duration: 10m 05s)

gerritbot added a comment.Tue, Nov 18, 3:16 PM

Change #1206891 had a related patch set uploaded (by Sergio Gimeno; author: Sergio Gimeno):

[mediawiki/extensions/GrowthExperiments@master] fix(ReviseToneExperimentInteractionLogger): prevent breaking homepage for unsampled users

https://gerrit.wikimedia.org/r/1206891

Michael edited projects, added Growth-Team (FY2025-26 Q2 Sprint 4); removed Growth-Team (FY2025-26 Q2 Sprint 3).Tue, Nov 18, 5:39 PM
Michael moved this task from Incoming to Code Review on the Growth-Team (FY2025-26 Q2 Sprint 4) board.
gerritbot added a comment.Tue, Nov 18, 6:24 PM

Change #1206891 merged by jenkins-bot:

[mediawiki/extensions/GrowthExperiments@master] fix(ReviseToneExperimentInteractionLogger): prevent breaking homepage for unsampled users

https://gerrit.wikimedia.org/r/1206891

gerritbot added a comment.Tue, Nov 18, 6:28 PM

Change #1206936 had a related patch set uploaded (by Sergio Gimeno; author: Sergio Gimeno):

[mediawiki/extensions/GrowthExperiments@wmf/1.46.0-wmf.3] fix(ReviseToneExperimentInteractionLogger): prevent breaking homepage for unsampled users

https://gerrit.wikimedia.org/r/1206936

ReleaseTaggerBot edited projects, added MW-1.46-notes (1.46.0-wmf.4; 2025-11-25); removed MW-1.46-notes (1.46.0-wmf.3; 2025-11-19).Tue, Nov 18, 7:00 PM
gerritbot added a comment.Tue, Nov 18, 11:52 PM

Change #1205188 merged by jenkins-bot:

[mediawiki/extensions/GrowthExperiments@master] analytics(ReviseTone): log an edit_save event for users in experiment

https://gerrit.wikimedia.org/r/1205188

Sgs moved this task from Code Review to Doing on the Growth-Team (FY2025-26 Q2 Sprint 4) board.Wed, Nov 19, 9:54 AM

Moving this to QA while I self-QA it and get @Iflorez's feedback.

gerritbot added a comment.Wed, Nov 19, 2:29 PM

Change #1206936 merged by jenkins-bot:

[mediawiki/extensions/GrowthExperiments@wmf/1.46.0-wmf.3] fix(ReviseToneExperimentInteractionLogger): prevent breaking homepage for unsampled users

https://gerrit.wikimedia.org/r/1206936

Stashbot added a comment.Wed, Nov 19, 2:30 PM

Mentioned in SAL (#wikimedia-operations) [2025-11-19T14:30:50Z] <sgimeno@deploy2002> Started scap sync-world: Backport for [[gerrit:1206936|fix(ReviseToneExperimentInteractionLogger): prevent breaking homepage for unsampled users (T405177)]], [[gerrit:1207118|fix(MigrateMentorStatusAway): ensure migration respects date format (T409170)]]

Stashbot mentioned this in T409170: Run MigrateMentorStatusAway migration script.Wed, Nov 19, 2:30 PM
Maintenance_bot removed a project: Patch-For-Review.Wed, Nov 19, 2:31 PM
Stashbot added a comment.Wed, Nov 19, 2:35 PM

Mentioned in SAL (#wikimedia-operations) [2025-11-19T14:35:28Z] <sgimeno@deploy2002> sgimeno: Backport for [[gerrit:1206936|fix(ReviseToneExperimentInteractionLogger): prevent breaking homepage for unsampled users (T405177)]], [[gerrit:1207118|fix(MigrateMentorStatusAway): ensure migration respects date format (T409170)]] synced to the testservers (see https://wikitech.wikimedia.org/wiki/Mwdebug). Changes can now be verified there.

Stashbot added a comment.Wed, Nov 19, 2:40 PM

Mentioned in SAL (#wikimedia-operations) [2025-11-19T14:40:00Z] <sgimeno@deploy2002> Finished scap sync-world: Backport for [[gerrit:1206936|fix(ReviseToneExperimentInteractionLogger): prevent breaking homepage for unsampled users (T405177)]], [[gerrit:1207118|fix(MigrateMentorStatusAway): ensure migration respects date format (T409170)]] (duration: 09m 09s)

ReleaseTaggerBot edited projects, added MW-1.46-notes (1.46.0-wmf.3; 2025-11-19); removed MW-1.46-notes (1.46.0-wmf.4; 2025-11-25).Wed, Nov 19, 3:00 PM
gerritbot added a comment.Thu, Nov 20, 11:52 AM

Change #1207825 had a related patch set uploaded (by Sergio Gimeno; author: Sergio Gimeno):

[mediawiki/extensions/GrowthExperiments@master] ReviseToneExperimentEditIngress: add debug statements

https://gerrit.wikimedia.org/r/1207825

gerritbot added a project: Patch-For-Review.Thu, Nov 20, 11:52 AM
Sgs mentioned this in T402707: Set up A/B test for “Revise Tone” Structured Task.Thu, Nov 20, 12:53 PM
gerritbot added a comment.Thu, Nov 20, 2:30 PM

Change #1207825 merged by jenkins-bot:

[mediawiki/extensions/GrowthExperiments@master] ReviseToneExperimentEditIngress: add debug statements

https://gerrit.wikimedia.org/r/1207825

Maintenance_bot removed a project: Patch-For-Review.Thu, Nov 20, 2:31 PM
ReleaseTaggerBot edited projects, added MW-1.46-notes (1.46.0-wmf.4; 2025-11-25); removed MW-1.46-notes (1.46.0-wmf.3; 2025-11-19).Thu, Nov 20, 3:00 PM
gerritbot added a comment.Thu, Nov 20, 3:12 PM

Change #1207882 had a related patch set uploaded (by Sergio Gimeno; author: Sergio Gimeno):

[operations/mediawiki-config@master] EventStreamConfig: drop revision and namespace id from contributors.experiments

https://gerrit.wikimedia.org/r/1207882

gerritbot added a project: Patch-For-Review.Thu, Nov 20, 3:12 PM
gerritbot added a comment.Thu, Nov 20, 3:14 PM

Change #1207883 had a related patch set uploaded (by Sergio Gimeno; author: Sergio Gimeno):

[mediawiki/extensions/GrowthExperiments@master] instrumentation(ReviseTone): manually collect revision and namespace

https://gerrit.wikimedia.org/r/1207883

gerritbot added a comment.Thu, Nov 20, 6:43 PM

Change #1207882 merged by jenkins-bot:

[operations/mediawiki-config@master] EventStreamConfig: drop revision and namespace id from contributors.experiments

https://gerrit.wikimedia.org/r/1207882

gerritbot added a comment.Fri, Nov 21, 11:07 AM

Change #1208303 had a related patch set uploaded (by Sergio Gimeno; author: Sergio Gimeno):

[mediawiki/extensions/GrowthExperiments@master] instrumentation(ReviseTone): add SE enabled to context on homepage visits

https://gerrit.wikimedia.org/r/1208303

gerritbot added a comment.Fri, Nov 21, 11:34 AM

Change #1207883 merged by jenkins-bot:

[mediawiki/extensions/GrowthExperiments@master] instrumentation(ReviseTone): manually collect revision and namespace

https://gerrit.wikimedia.org/r/1207883

gerritbot added a comment.Mon, Nov 24, 10:43 AM

Change #1210526 had a related patch set uploaded (by Sergio Gimeno; author: Sergio Gimeno):

[operations/mediawiki-config@master] [beta] GrowthExperiments: increase to log level to debug

https://gerrit.wikimedia.org/r/1210526

gerritbot added a comment.Mon, Nov 24, 2:06 PM

Change #1210526 merged by jenkins-bot:

[operations/mediawiki-config@master] [beta] GrowthExperiments: increase log level to debug

https://gerrit.wikimedia.org/r/1210526

gerritbot added a comment.Mon, Nov 24, 3:23 PM

Change #1210610 had a related patch set uploaded (by Sergio Gimeno; author: Sergio Gimeno):

[mediawiki/extensions/GrowthExperiments@master] anlytics(ReviseTone): use ReviseToneExperimentInteractionLogger instead of experiment

https://gerrit.wikimedia.org/r/1210610

Sgs moved this task from Doing to Code Review on the Growth-Team (FY2025-26 Q2 Sprint 4) board.Mon, Nov 24, 3:23 PM
gerritbot added a comment.Mon, Nov 24, 3:55 PM

Change #1210619 had a related patch set uploaded (by Sergio Gimeno; author: Sergio Gimeno):

[mediawiki/extensions/GrowthExperiments@master] analytics(ReviseTone): track suggestion-shown interaction

https://gerrit.wikimedia.org/r/1210619

gerritbot added a comment.Thu, Nov 27, 10:03 AM

Change #1210610 abandoned by Sergio Gimeno:

[mediawiki/extensions/GrowthExperiments@master] anlytics(ReviseTone): use ReviseToneExperimentInteractionLogger instead of experiment

Reason:

Squashed in I6dbb137f32ca88fd1baeecd89e546a41235ea8d8

https://gerrit.wikimedia.org/r/1210610

gerritbot added a comment.Thu, Nov 27, 10:10 AM

Change #1208303 abandoned by Sergio Gimeno:

[mediawiki/extensions/GrowthExperiments@master] instrumentation(ReviseTone): fix stream for edits and refine exposure

Reason:

Messed change-ids, squashed in https://gerrit.wikimedia.org/r/c/mediawiki/extensions/GrowthExperiments/+/1210619

https://gerrit.wikimedia.org/r/1208303

gerritbot added a comment.Thu, Nov 27, 12:22 PM

Change #1212128 had a related patch set uploaded (by Sergio Gimeno; author: Sergio Gimeno):

[mediawiki/extensions/GrowthExperiments@wmf/1.46.0-wmf.4] instrumentation(ReviseTone): fix stream for edits and refine exposure

https://gerrit.wikimedia.org/r/1212128

gerritbot added a comment.Thu, Nov 27, 2:17 PM

Change #1212128 merged by jenkins-bot:

[mediawiki/extensions/GrowthExperiments@wmf/1.46.0-wmf.4] instrumentation(ReviseTone): fix stream for edits and refine exposure

https://gerrit.wikimedia.org/r/1212128

Stashbot added a comment.Thu, Nov 27, 2:17 PM

Mentioned in SAL (#wikimedia-operations) [2025-11-27T14:17:58Z] <sgimeno@deploy2002> Started scap sync-world: Backport for [[gerrit:1212106|fix(ReviseTone): only initialize once]], [[gerrit:1212108|fix(ReviseTone): render behind EditNotice on mobile]], [[gerrit:1212128|instrumentation(ReviseTone): fix stream for edits and refine exposure (T405177 T406252)]]

Stashbot added a comment.Thu, Nov 27, 2:19 PM

Mentioned in SAL (#wikimedia-operations) [2025-11-27T14:19:53Z] <sgimeno@deploy2002> sgimeno, migr: Backport for [[gerrit:1212106|fix(ReviseTone): only initialize once]], [[gerrit:1212108|fix(ReviseTone): render behind EditNotice on mobile]], [[gerrit:1212128|instrumentation(ReviseTone): fix stream for edits and refine exposure (T405177 T406252)]] synced to the testservers (see https://wikitech.wikimedia.org/wiki/Mwdebug). Changes can now be verified there.

gerritbot added a comment.Thu, Nov 27, 2:26 PM

Change #1210619 merged by jenkins-bot:

[mediawiki/extensions/GrowthExperiments@master] instrumentation(ReviseTone): fix stream for edits and refine exposure

https://gerrit.wikimedia.org/r/1210619

Stashbot added a comment.Thu, Nov 27, 2:28 PM

Mentioned in SAL (#wikimedia-operations) [2025-11-27T14:28:43Z] <sgimeno@deploy2002> Finished scap sync-world: Backport for [[gerrit:1212106|fix(ReviseTone): only initialize once]], [[gerrit:1212108|fix(ReviseTone): render behind EditNotice on mobile]], [[gerrit:1212128|instrumentation(ReviseTone): fix stream for edits and refine exposure (T405177 T406252)]] (duration: 10m 46s)

Maintenance_bot removed a project: Patch-For-Review.Thu, Nov 27, 2:30 PM
Sgs moved this task from Code Review to QA on the Growth-Team (FY2025-26 Q2 Sprint 4) board.Thu, Nov 27, 2:42 PM
Urbanecm_WMF edited projects, added Growth-Team (FY2025-26 Q2 Sprint 5); removed Growth-Team (FY2025-26 Q2 Sprint 4).Tue, Dec 2, 5:47 PM
Urbanecm_WMF moved this task from Incoming to QA on the Growth-Team (FY2025-26 Q2 Sprint 5) board.
Content licensed under Creative Commons Attribution-ShareAlike (CC BY-SA) 4.0 unless otherwise noted; code licensed under GNU General Public License (GPL) 2.0 or later and other open source licenses. By using this site, you agree to the Terms of Use, Privacy Policy, and Code of Conduct. · Wikimedia Foundation · Privacy Policy · Code of Conduct · Terms of Use · Disclaimer · CC-BY-SA · GPL · Credits