[01:47:42] i was thinking we should have a channel for extension updates [02:02:35] That would be nice. [04:11:50] how so [04:33:39] For extension updates that don't warrant a minor announcement, we can batch them and send all of them at once? [04:36:24] mwdeploy integration? [06:53:28] BlankEclair: oh fun [12:24:52] [1/2] not a bad idea but its nicer to get the info out immediately [12:24:53] [2/2] as with my yesterday's DN upgrade, people didn't know it could suddenly embed images [12:27:15] I'd say they might warrant a minor announcement actually [12:28:10] people subscribe to that channel to get news about these small changes, we should give it to them [14:56:38] Hmmm... Between the two, not sure. I could see an argument for a discrete channel for cleanliness/backsearch + if upgrades are frequent enough to muddy today's minor uses of minor announcements. [16:21:11] some kind of tech changelog channel might be useful, e.g. when a setting is added/removed, an extension was upgraded and has new features or breaking changes, etc [16:39:24] ^ [17:16:39] Hmmm, Kinda the purpose of techops, though that itself is muddied with general discussion and the occasional icinga flood [17:42:50] 90% of stuff in #tech-ops, #tech and Github commit logs are not relevant to wiki admins/bureaucrats/users [17:48:58] e.g. nobody except for tech really cares if maintenance scripts are run on individual wikis, a server is running out of disk space or somebody is refactoring an extension on github [17:49:43] and I think relevant changes like the ones I mentioned five messages above happen too often to warrant a post in#minor-announcements [17:50:51] we could compile noteworthy ones weekly [17:51:42] that's a good idea, similar to WMF's tech news maybe