The 7.1.x maintenance line put out a call for release managers, with 7.1.1 scheduled across the first three weeks of September. If you have ever considered contributing to core and decided you did not know enough, this is the part of the process that most directly contradicts that.
The unglamorous release
A major release is where features land. A maintenance release is where the consequences get cleaned up: regressions, edge cases that only appear at scale, bugs known at release that did not justify holding it.
They are the reason it is reasonable to run WordPress in production at all. And the point most developers miss is that the version you actually want your clients on is rarely x.x.0. It is x.x.1, a few weeks later, once the first wave of real installs has surfaced what testing did not.
What the job involves
Release management is process work rather than deep technical work. Confirming which tickets are in scope, checking they are actually committed, running the packaging steps, communicating dates. It rewards being organised and reliable much more than it rewards knowing the block editor internals.
That makes it one of the few core roles a competent agency developer can do well without first spending a year reading source. It is also a role the project is perennially short-handed on, which is why the call goes out.
The lower bar, if you are not volunteering
Test the release candidates. A maintenance RC needs people running it against unusual setups: odd hosting stacks, large multisite installs, heavily filtered themes. Those are exactly the configurations core contributors do not have sitting around.
Put an RC on one non-critical client site, use it for a few days, report anything that breaks with enough detail to reproduce. That is the whole contribution and it is genuinely valuable.
What this says about your update cadence
There is a habit in agency work of treating updates as an interruption, batching them and applying them quarterly. The maintenance line is the argument against it. Security fixes ship in these releases, and the gap between a public disclosure and automated exploit attempts is now measured in hours. A quarterly cycle is not caution. It is an unpatched site for eighty-nine days out of ninety.
