I responded more thoroughly on that task, but tldr: it was closed prematurely which made me thing it had been backported. rc.1 has been released like 10 minutes ago, but it'll make it into the final release.
... rc.1 has been released like 10 minutes ago, but it'll make it into the final release.
I'm more concerned that there are other PR's that haven't back-ported, so running a query of some kind should avoid manual intervention (or someone remembering that this hasn't happened yet).
There's no query that can be done. See my comment on T167946#3417390 -- the mapping is complex and has to be manually curated. If people need things backported, they get tagged with MW-1.29-release and we get them backported. If people don't care enough to get things backported then there's precious little I can do to help. I get thousands of bug/gerrit notifs a week and I cannot possibly keep track of everything in the MW ecosystem. In the case of T167946, the task was closed prematurely and I assumed--not unreasonably--that all the work was done.
It is on developers and change drivers to get their fixes to all the right places at the end of the day, especially for subsystems that are less frequently used/understood 😁
Theoretically if you searched for tasks tagged MW-1.29-release without a MW-1.29-release-notes tag it might work, but I can't seem to get Phabricator to just include MW-1.29-release without any of its subprojects: https://phabricator.wikimedia.org/maniphest/query/.njVirn9OXaF/#R
For 1.28, it went like this:
- First release candidate 2016-11-02
- Second release candidate 2016-11-17
- Stable release 2016-11-28
Obviously a serious issue might be found and create a delay. If so, I assume it is a low priority for the full-time developers, who are dealing with 1.30 betas.