[PostGIS] #5736: latest releases md5 mismatch

[PostGIS]

#5736: latest releases md5 mismatch
-------------------------+--------------------------------------
  Reporter:  strk        |      Owner:  robe
      Type:  defect      |     Status:  reopened
  Priority:  medium      |  Milestone:  Website Management, Bots
 Component:  management  |    Version:  3.4.x
Resolution:              |   Keywords:
-------------------------+--------------------------------------
Comment (by robe):

 I think the other way that this issue happens is that debbie builds a
 release tar ball twice.

 Once for the branch and once for the tag.

 So if the releaser is in a rush, they might download the one that is
 generated by the branch release, and that on occasion might not be the
 tagged yet, and then that release gets rebuilt on tag.

 Can you think of an easy way to prevent tagged builds being built from
 branches?  I'm thinking since debbie has a dedicated script, she could
 just verify if she is in a tagged branch or regular branch, and just not
 copy the artifacts to the website.
-- 
Ticket URL: <https://trac.osgeo.org/postgis/ticket/5736#comment:21>
PostGIS <http://trac.osgeo.org/postgis/>
The PostGIS Trac is used for bug, enhancement & task tracking, a user and developer wiki, and a view into the subversion code repository of PostGIS project.