Reading/Web/Release Manager updates
This records the current state of chores as defined in the chore list. View team norms
Chore | Who | Status | Notes | Last updated |
---|---|---|---|---|
Monday | ||||
Browser tests | All | ✅ | All green
Previously: Popups failing due to https://phabricator.wikimedia.org/T370460#10057377 |
BWang (WMF) (talk) 15:09, 21 October 2024 (UTC) |
Visual regression | Developers | ✅ |
Some expected visuals changes from the appearance menu, and some false errors from noise DO NOT EDIT HERE PLEASE UPDATE Reading/Web/Release timeline/Visual Changes with any expected or unexpected changes.[1] NOTE: If doing this chore late, please take note of the dates of reports on pixel instance. You will need to run the regression tests locally. This check is for the release that goes out this week not next week.
|
BWang (WMF) (talk) 15:09, 21 October 2024 (UTC) |
Wednesday | ||||
Review dashboard | All | ✅ | Run through the list in "Needs triage" and tag tasks with the relevant team. If in doubt add tag #readers-web-backlog to every task here. | BWang (WMF) (talk) 15:10, 24 October 2024 (UTC) |
Logstash (client errors) | Developers | ✅ | Check group 0 and 1 wikis "Top 10 errors (group 1) widget" on dashboard. Flag any significant spikes as potential deploy blockers. Anything with error rate that is not a gadget issue over 1000 should have a corresponding bug and is worth flagging to the team. | BWang (WMF) (talk) 15:10, 24 October 2024 (UTC) |
Thursday/Friday | ||||
Logstash (client errors) | Developers | ✅ | Previous: Filed https://phabricator.wikimedia.org/T375417
Do not remove these instructions: Bugs with > 1400 occurrences in 7 days: 1) create a ticket (unless gadget - in which case use slack channel or gadget talk page). 2) Create a filter for the bug labeling the filter with the open ticket number if it belongs to. 3) If the bug does not belong to us, enable the filter by default and exclude it from the view. If the bug belongs to us, disable the filter. For banner errors see meta:CentralNotice/FAQ Investigate bugs < 100 optional if have time and interested. When investigating bugs filter those errors out ideally using a stack trace wildcard. If a bug belongs to reading web change the label to the phab ticket number. If not add it to one of the existing team or gadget filters. As part of chores we'll check and remove existing pins where the task has been resolved. The less pins at the top the cl |
BWang (WMF) (talk) 15:10, 24 October 2024 (UTC) |
Logstash (PHP errors) | Developers | ✅ | <Create tasks for anything notable that you are use relates to our work> | BWang (WMF) (talk) 15:10, 24 October 2024 (UTC) |
EventLogging validation errors | Developers | ✅ | All good! Previously (open tasks): None |
BWang (WMF) (talk) 15:10, 24 October 2024 (UTC) |
Friday | ||||
Handover | Please repeat Monday/Wednesday tasks of checking Pixel, reviewing dashboard browser tests and pass over to the next person. | JDrewniak (WMF) (talk) 19:15, 27 September 2024 (UTC) |
Additional roles
edit- The release manager is accountable for updating the team on the state of the current deploy (whether the train is blocked, whether any new bugs have been flagged that relate to the team or whether everything is going to plan)
- The release manager is accountable for any e-mail alerts with subject [FIRING]
- Email's relating to client errors:
- Make sure the alert is understood and bug(s) are filed
- If a gadget is related, make sure the gadget author is notified or the gadget is fixed
- Update the alerting threshold to stop the e-mail alert
- Email's relating to QuickSurveys
- Make sure we understand which quicksurvey got enabled and where
- Review the Grafana graphs to see if this is impacting performance in any way (QuickSurveys pulls down the entirety of Codex on the page)
- Find out when the QuickSurvey is going to be disabled
- Update the alerting threshold to stop the e-mail alert
- File a ticket associated with the deployment task with #Web-Team-Backlog to remove the alert
- Email's relating to perforance
- Review the Grafana graphs
- Open bug(s) if necessary documenting any regressions
- Update the alerting threshold if necessary
- Email's relating to client errors:
- The release manager is accountable for tagging any deployment blockers and making sure UBN's get handled (they do not necessarily need to deploy the patch themselves but they must make sure the deploy happens where needed.
Archived chores
editOther | ||||
Check talk pages | All | ✅ | Archived. Will be done outside chore wheel from now on. | |
Say something nice to a team member! | All | 🎉 | Archived but please still do this :) | |
Document notable events | All | 🎉 | Archived. We will do this as part of sign off steps on tasks from now on |
A11y tests | ✅ | Moving temporarily into archived unto flakiness is fixed
Previously
Visit the a11y grafana dashboard to see the metrics over time. If there are any changes, look at the daily reports in Jenkins to investigate. Note: The "logged in" test will sometimes fluctuate due to different notices/gadgets being enabled in beta cluster. Changes can be made to the config to hide problematic elements and improve consistency. |
BWang (WMF) (talk) 15:34, 18 May 2023 (UTC) |
Review the Reading Web Backlog | ✅ | Will be done as part of grooming meeting | Jdlrobson (talk) 21:27, 9 February 2023 (UTC) |
Check volunteer patches on Phab | ✅ | We now have a grooming meeting. This will be covered there. | Jdlrobson (talk) 21:27, 9 February 2023 (UTC) |
Check patches on Gerrit have attention or hashtags | ✅ | We now have a grooming meeting. This will be covered there.
|
Jdlrobson (talk) 21:27, 9 February 2023 (UTC) |
Check Slack for bug reports for code in production without Phabricator ticket | ✅ | We now have a grooming meeting. This will be covered there.
____ Often we might report bugs initially on Slack and submit patches. For issues that have hit production, our team norm is to make sure there a bug is created so that the issue can be tracked. Check the back scroll for the last week and create Phabricator tasks where needed. |
Jdlrobson (talk) 21:27, 9 February 2023 (UTC) |
Ensure goals are current | ✅ | Asked in standup today. | Jdlrobson (talk) 21:32, 5 January 2023 (UTC) |
Page previews dashboard | ✅ | Archived in favor of alerting.
Previously:
|
NRay (WMF) (talk) 19:36, 17 February 2023 (UTC) |
Generic dashboard | ✅ | Archived in favor of alerting.
Previously:
|
NRay (WMF) (talk) 19:36, 17 February 2023 (UTC) |
performance dashboard | ✅ | Archived in favor of alerting.
Previously:
Please note anything significant on Reading/Web/Notable_incidents |
NRay (WMF) (talk) 19:36, 17 February 2023 (UTC) |
Search performance dashboard | Looks good
Previously:
|
BWang (WMF) (talk) 18:09, 6 April 2023 (UTC) |
Helpers
editStatus fields:
✅ | is fine |
⚠️ | needs attention |
🚨 | is on fire |
🎉 | For your attention but positive |
Last updated (Use four tildes to autosign)
- ↑ Reminder: Ensure you have run Pixel against the upcoming release number to avoid missing changes over the weekend
Visit https://pixel.wmcloud.org/ to see the latest visual diff between the latest release and master. This report is updated every hour. Update Reading/Web/Release timeline/Visual Changes with any expected or unexpected changes. If needed, you can also run the following locally on the latest pixel version to compare the latest release to master:./pixel.js reference -b latest-release ./pixel.js test