search

epics-base / p4p

Python bindings for the PVAccess network client and server.
BSD 3-Clause "New" or "Revised" License
27 stars 38 forks source link

GitHub isn't showing all your tags as releases #64

Closed anjohnson closed 3 years ago

anjohnson commented 3 years ago

Hi Michael, You've applied 3 new tags to the p4p repo since version 3.4.2 last January, but I just noticed that GitHub's Releases page isn't showing the newer ones as published releases. Version 3.4.2 also appears as the latest release in the right-hand column of the main repo page: image

Thought you might want to take a look at that and update it sometime; if you make use of GitHub's release process at all it seems you have to continue to do so every time to keep the website's "Latest" badge up to date.

mdavidsaver commented 3 years ago

I think github will let me delete the "release" for the two tags which I did mark. This will hopefully then revert the releases pages to showing a list of tags.

mdavidsaver commented 3 years ago

Ok, it is done.

Also, is this just a question of notification for you? Rather than taking a tar blob from github.com, I had assumed that release managers at large sites would start from a local git clone, with verification of a signed tag.

anjohnson commented 3 years ago

Thanks. Actually it wasn't notifications (yet), but IIRC you do have a pointer to the releases page in your doc's, and that seemed a bit confusing to not have the "latest" appear to be marked as that; the project was looking slightly abandoned before.