Updated Portfile merged 17 hours ago, still not distributed?

[Jim DeLaHunt]

Hello, folks:

I submitted a PR <https://github.com/macports/macports-ports/pull/28546> 
recently, and it was merged into master 17 hours ago. I am a bit 
surprised that when I do `sudo port selfupdate` on my local machine, I 
still get the previous Portfile, not the one merged 17 hours ago. I 
realise that distribution is not instantaneous, but I expected it to 
take a few hours at most.

What delay should I expect between when an updated Portfile is merged 
into the `master` branch of github.com/macports/macports-ports/, and 
when I receive it via `sudo port selfupdate`?

The new Portfile has no `revision` keyword, so like the previous 
Portfile it is implicitly revision 0. Does this make a difference?

(I did not increment the revision because the port did not build before, 
in the presence of port gtk3 +quartz, though it did build in the 
presence of port gtk3 -quartz +x11. Did I choose correctly?)

I benefit from all the work you all put into improving Portfiles, so I 
am honoured to join your ranks. And maybe I'm a wee bit eager to benefit 
from my own work :-).

Best regards,
     —Jim DeLaHunt

-- 
.    --Jim DeLaHunt, Vancouver, Canada