danie...@apache.org wrote on Tue, 08 Jan 2019 12:03 +0000: > Log: > * tools/upcoming.py > (copyfrom_revision_of_previous_tag_of_this_stable_branch): > Determine the latest release by checking dist/release/, not by checking > tags, in order to also show changes that have been merged into a patch > release that has not been announced yet. > > This change will cause tonight's bot run to effectively revert r1850708 (and > add Monday's merge to the output as well), re-adding all the merges that > went into 1.11.1 to the Web site — which is correct, since 1.11.1 has not yet > been published.
There is still a minor race condition here: when 1.11.1 artifacts are moved to dist/release/, the Website will stop showing merges that went into 1.11.1 even before the download page and mirrors are updated to 1.11.1. I suppose we can live with that, but if anyone has ideas for improving the situation... Cheers, Daniel
