[go: up one dir, main page]

Page MenuHomePhabricator

Release ping users from edit summary in production
Closed, ResolvedPublic1 Estimated Story Points

Description

Now that ping users from edit summary is on the beta cluster, we should get them on production after QA (T188465) is done.

Event Timeline

TBolliger set the point value for this task to 1.
TBolliger edited projects, added Community-Tech-Sprint; removed Community-Tech.
TBolliger subscribed.

Also: set a meeting to train Leon and Sam how to release.

TBolliger changed the task status from Open to Stalled.Mar 5 2018, 10:06 PM
TBolliger claimed this task.

Discussing release, given the edit summary length ongoing issue.

TBolliger changed the task status from Stalled to Open.Mar 6 2018, 12:06 AM
TBolliger removed TBolliger as the assignee of this task.

Not stalled. This already went out in TechNews, we will just want to announce on Village Pump immediately when this releases to avoid any backlash.

If it's easy (which I think @MaxSem said it was), could we possibly do T189067 before releasing? Then we can let folks know they have a way to link without pinging, and this would address the Twinkle use case, specifically.

If it's a small and low-risk task, I'm all for it. But I think we can release without it and add it as a fast follow if there is any risk.

Change 417031 had a related patch set uploaded (by MaxSem; owner: MaxSem):
[mediawiki/extensions/Echo@master] Allow to avoid pinging from summaries by prefixing with :

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

Change 417329 had a related patch set uploaded (by MaxSem; owner: MaxSem):
[operations/mediawiki-config@master] Enable ping from edit summary in prod

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

Change 417329 merged by jenkins-bot:
[operations/mediawiki-config@master] Enable ping from edit summary in prod

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

Niharika claimed this task.
Niharika moved this task from Ready to Q1 2018-19 on the Community-Tech-Sprint board.

Wooo! This is deployed in production now! Thanks @MaxSem for all his work on this.