I think we should do this Q4, it will impact quality of data if we space updates too much.
|Resolved||fdans||T189230 Update UA parser|
|Resolved||fdans||T192463 Update version of ua-parser in refinery source|
|Resolved||Nuria||T192464 Update ua-parser package. Both uap-java and uap-core|
|Duplicate||fdans||T192465 Pull wmf ua-parser-core from the upstream repo|
|Resolved||fdans||T192529 Update version of ua-parser in eventlogging|
|Resolved||fdans||T193578 Assess impact of ua-parser update on core metrics|
Thanks for working on this! As @Nuria points out in the task description, it looks important for data quality to keep this updated. Back in 2015 (T106134), @dr0ptp4kt suggested to automate these updates. Is that possible?
Once this task here is complete, we should update the documentation at https://wikitech.wikimedia.org/wiki/Analytics/Data_Lake/Traffic/Webrequest#Changes_and_known_problems_since_2015-03-04 and other suitable places with the deployment date, a link to a concrete diff between the old and new regexes, and the outcome of T193578: Assess impact of ua-parser update on core metrics.