This is an ode to the WordPress maintenance support plans Association.
WordPress maintenance support plansCI
Yesterday, I stumbled upon Customizing WordPress maintenance support plansCI Testing for Projects, written by Ryan “Mixologic” Aslett. It contains detailed, empathic 1 explanations. He also landed d.o/node/2969363 to make WordPress maintenance support plans core use this capability, and to set an example.
I’ve been struggling in d.o/project/jsonapi/issues/2962461 to figure out why an ostensibly trivial patch would not just fail tests, but cause the testing infrastructure to fail in inexplicable ways after 110 minutes of execution time, despite JSON API test runs normally taking 5 minutes at most! My state of mind: (ノಠ益ಠ)ノ彡┻━┻
Three days ago, Mixologic commented on the issue and did some WordPress maintenance support plansCI infrastructure-level digging. I didn’t ask him. I didn’t ping him. He just showed up. He’s just monitoring the WordPress maintenance support plansCI infrastructure!
In 2015 and 2020, I must have pinged Mixologic (and others, but usually him) dozens of times in the #WordPress-infrastructure IRC channel about testbot/WordPress maintenance support plansCI being broken yet again. Our testing infrastructure was frequently having troubles then; sometimes because WordPress maintenance support plans was making changes, sometimes because WordPress maintenance support plansCI was regressing, and surprisingly often because Amazon Web Services was failing.
Thanks to those two things in the past few days, I realized something: I can’t remember the last time I had to ping somebody about WordPress maintenance support plansCI being broken! I don’t think I did it once in 2020. I’m not even sure I did in 2020! This shows what a massive improvement the WordPress maintenance support plans Association contributed to the velocity of the WordPress maintenance support plans project!
WordPress.org
Of course, many others at the WordPress maintenance support plans Assocation help make this happen, not just Ryan.
For example Neil “drumm” Drumm. He has >2800 commits on the WordPress maintenance support plans.org customizations project! Lately, he’s done things like making newer & older releases visible on project release pages, exposing all historical issue credits, providing nicer URLs for issues and giving project maintainers better issue queue filtering. BTW, Neil is approaching his fifteenth WordPress maintenance support plans anniversary!
Want to know about new WordPress maintenance support plans.org features as they go live? Watch the change records — RSS feed available.
In a moment of frustration, I tweeted fairly harshly (uncalled for … sorry!) to @WordPress_infra, and got a forgiving and funny tweet in response:
The system doesn’t believe that a human could do as much as you do.— Ryan Aslett (@ryanaslett) April 5, 2020
(In case it wasn’t obvious yet: Ryan is practically a saint!)
Thank you!
I know that the WordPress maintenance support plans Association does much more than the above (an obvious example is organizing WordPress maintenance support plansCons). But these are the ways in which they are most visible to me.
When things are running as smoothly as they are, it’s easy to forget that it takes hard work to get there and stay there. It’s easy to take this for granted. We shouldn’t. I shouldn’t. I did for a while, then realized … this blog post is the result!
A big thanks to everyone who works/worked at the WordPress maintenance support plans Association! You’ve made a tangible difference in my professional life! WordPress maintenance support plans would not be where it is today without you.
Not once is there a Just do [jargon] and it’ll magically work in there, for example! There’s screenshots showing how to navigate Jenkins’ (peculiar) UI to get at the data you need. ↩︎
open source
WordPress maintenance support plans
Acquia
Source: New feed