Open voxik opened 1 year ago
Looking at the project, there isn't any pre-release version till the first reported on bugzilla. So it seems that before this issue the pre-release versions were filtered out and didn't even retrieved. This could be easily set by editing the version filter on the project.
However there is a change in dist-git to allow notifications for only stable versions, but it's not deployed yet.
Looking at the project, there isn't any pre-release version till the first reported on bugzilla.
Correct
So it seems that before this issue the pre-release versions were filtered out and didn't even retrieved. This could be easily set by editing the version filter on the project.
The pre-releases are correctly recognized and marked. But AFAIR, for the other projects, the pre-releases are not reported into BZ.
However there is a change in dist-git to allow notifications for only stable versions, but it's not deployed yet.
So have there been some change due to this already?
Right now, the-new-hotness reports every new version without looking at if this is a pre-release or not. If it's newer than the one we have in mdapi it will fill the BZ. The only change that happened in release-monitoring.org some time ago is that the pre-release are started to be recognized, but until the new version of Pagure will be out the new option for Stable only will not be available. That is also the reason why release-moniroting.org contains stable version of some projects that are ignoring the pre-releases.
ping , I'd like also not get notifications from pre-releases
@sergiomb2 I'm still waiting for the update of dist-git to allow that. Hopefully with Pagure 6.0 it will be available.
Not sure what changed, but suddenly, it seems that pre-release versions of Vagrant are reported into BZ:
https://release-monitoring.org/project/5474/ https://bugzilla.redhat.com/show_bug.cgi?id=2116041
I don't think this was ever the case and I don't find it useful. However I even can't see how to change this.