Page MenuHomePhabricator

Deploy Config to Introduce Manual Topic Subscriptions as Beta Feature at Phase 1 Wikis
Closed, ResolvedPublic

Description

This task is about making manual topic subscriptions available as a beta feature at the ===Phase 2 wikis listed below

Deployment timing

Wednesday, 18 August during the Morning backport window (18:00 - 19:00 UTC)

Phase 1 wikis

via T286096.

Wiki code
Commonsnote
Wikidatanote

Requirements

For people at the "Phase 1 wikis" above who have the Discussion tools beta feature enabled, they will see the following:

  1. In Special:Preferences#mw-prefsection-betafeatures: the Discussion tools beta feature should contain a list item that reads: Receive notifications when new comments are added in sections you have subscribed to.
  2. In Special:Preferences#mw-prefsection-editing: a new setting within the Discussion pages section that contains a setting titled Enable topic subscription and this setting should be enabled by default
  3. On a talk page with at least one ==H2==, a [ subscribe ] affordance should appear next to it

Done

  • All ===Requirements are met

Event Timeline

ppelberg renamed this task from Deploy config to introduce manual topic subscriptions as Beta Feature at Phase 1 projects to Deploy Config to Introduce Manual Topic Subscriptions as Beta Feature at Phase 1 Wiikis.Aug 12 2021, 1:14 AM
ppelberg renamed this task from Deploy Config to Introduce Manual Topic Subscriptions as Beta Feature at Phase 1 Wiikis to Deploy Config to Introduce Manual Topic Subscriptions as Beta Feature at Phase 1 Wikis.Aug 17 2021, 12:23 AM
ppelberg updated the task description. (Show Details)
ppelberg added a subscriber: matmarex.

Adding deployment date (Wednesday, 18 August) to task description. cc @matmarex

Change 713491 had a related patch set uploaded (by Bartosz Dziewoński; author: Bartosz Dziewoński):

[operations/mediawiki-config@master] Enable DiscussionTools' topicsubscription as beta feature on phase 1 wikis

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

(Note that the fixes for the two release blockers, T286620 and T286954, will be deployed with the 1.37.0-wmf.19 train deployment, which is scheduled an hour after our config deployment. I think this is okay.)

(Note that the fixes for the two release blockers, T286620 and T286954, will be deployed with the 1.37.0-wmf.19 train deployment, which is scheduled an hour after our config deployment. I think this is okay.)

+1; T286620 and T286954 getting deployed an hour after Manual Topic Subscriptions become available at Commons and Wikidata is fine. I'm glad you explicitly mentioned this, @matmarex.

An hour is really not much for such rather annoying than serious issues, but do you have plans for what to do if the train is blocked or gets rolled back? T281160: 1.37.0-wmf.19 deployment blockers looks clear right now, but who knows.

An hour is really not much for such rather annoying than serious issues, but do you have plans for what to do if the train is blocked or gets rolled back? T281160: 1.37.0-wmf.19 deployment blockers looks clear right now, but who knows.

We do not yet have a plan for the scenario you are describing. Although, you raising it here means we now know to talk about this in the team meeting we have scheduled before tomorrow's planned deployment window.

Change 713491 merged by jenkins-bot:

[operations/mediawiki-config@master] Enable DiscussionTools' topicsubscription as beta feature on phase 1 wikis

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

Mentioned in SAL (#wikimedia-operations) [2021-08-18T18:06:41Z] <urbanecm@deploy1002> Synchronized wmf-config/InitialiseSettings.php: 35113b617b3540242ac69a8285c54c70041bc14b: Enable DiscussionTools topicsubscription as beta feature on phase 1 wikis (T287800) (duration: 01m 25s)

An hour is really not much for such rather annoying than serious issues, but do you have plans for what to do if the train is blocked or gets rolled back? T281160: 1.37.0-wmf.19 deployment blockers looks clear right now, but who knows.

If it was necessary, we could undo our config change or backport the fixes for those tasks; but because the "blockers" are not that serious, we would probably just leave it deployed like that.