search

ualberta-smr / LibraryMetricScripts

Scripts to collect metrics from software libraries.
MIT License
4 stars 2 forks source link

Use releases instead of tags #13

Closed snadi closed 5 years ago

snadi commented 5 years ago

I recall there was a problem of using releases where the API was not returning all releases correctly. Fernando and I had a discussion a long time ago but I don't remember the details. Looking at the API now, if releases work properly, we should use releases for release frequency and also rule out pre-releases from the calculation

snadi commented 5 years ago

So I could actually replicate the problem.

When using get_releases from the github API for let's say junit-team/junit4, this is what is retuned (Ran on Aug 28, 2019):

release: r4.13-beta-3
release: r4.13-beta-2
release: r4.13-beta-1
release: r4.12
release: r4.12-beta-3
release: r4.12-beta-2
release: r4.11
release: r4.12-beta-1

Obviously, this is the not the whole list of releases for that library.

No releases are returned for cbeust/testng or qos-ch/slf4j

snadi commented 5 years ago

Ok, so it seems that even though looking at https://github.com/cbeust/testng/releases seems to suggest there are releases, these are actually no published. See https://stackoverflow.com/questions/26140372/cannot-get-releases-for-a-repo-with-the-github-api for a description of the problem. This is why we are using tags instead of releases.

Documenting this and closing the issue