Both Paul and I are in the US and have day jobs which require our attention over the volunteer work of tz.  I'm taking a little time over my lunch to note for everyone that, while it may be a little while until we can give our full attention to a new release, we are indeed acutely aware that there is a timely need here.

Unfortunately, many factors about the manner in which this has been handled means that we do not have a good workaround that would involve accepting certain tz updates while holding back others.  (That is, with these changes, 2023a would now be mostly correct, but not for the four-day period we're currently in the middle of; whereas 2023b would be more wrong thereafter.)  But considering how long downstream propagation of our data takes to get to end-users, though, there is not much more we could proactively do to stem the resulting discrepancies at this point, regardless of when we'll be able to release a further update.

All of that is to say the usual: There is no set schedule for releases, but we will certainly need a new one very soon.