Bug 2232417 - numpy release-monitoring seems to miss some upstream releases
Summary: numpy release-monitoring seems to miss some upstream releases
Keywords:
Status: ASSIGNED
Alias: None
Product: Fedora
Classification: Fedora
Component: numpy
Version: rawhide
Hardware: Unspecified
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Gwyn Ciesla
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-08-16 18:28 UTC by marcindulak
Modified: 2023-08-17 19:53 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: ---
Embargoed:


Attachments (Terms of Use)

Description marcindulak 2023-08-16 18:28:05 UTC
It looks like some numpy (maybe also other components) releases are not reflected on bugzilla.

For example, there is 1.25.2 release 2023-07-31 listed on https://release-monitoring.org/project/2509/, but I don't find it in bugzilla comment search https://bugzilla.redhat.com/buglist.cgi?columnlist=product%2Ccomponent%2Cassigned_to%2Cstatus%2Csummary%2Clast_change_time%2Cseverity%2Cpriority&component=numpy&list_id=13298697&longdesc=1.25.2&longdesc_type=allwordssubstr&order=status%2C%20priority%2C%20assigned_to%2C%20id%2C%20&product=Fedora&query_format=advanced

Is my search correct? I find some other versions this way, for example 1.24.0.dev0

Reproducible: Always

Comment 1 Gwyn Ciesla 2023-08-16 18:36:15 UTC
No, you're correct. I'll play with it and see what I can do, as well as starting work on 1.25.2. Thanks for the heads up!

Comment 2 marcindulak 2023-08-17 05:10:11 UTC
My point was different: I would expect the release monitoring to automatically mark existence of new releases on bugzilla.

Did you have release monitoring disabled periodically? This is controlled on https://src.fedoraproject.org/rpms/numpy
Otherwise we should open an issue at https://pagure.io/releng/new_issue

Comment 3 Gwyn Ciesla 2023-08-17 18:21:53 UTC
It does, and it's been enabled for as long as I'm aware. It's just that it doesn't see releases of older branches and believes that 2.0.0.dev0 is the most recent.

Comment 4 marcindulak 2023-08-17 19:53:13 UTC
Would you like to open an issue at https://pagure.io/releng/new_issue?

Release monitoring works for me - https://bugzilla.redhat.com/show_bug.cgi?id=2071356 kept adding comments about new releases until I closed the bug,
then a new bug was auto created when a new upstream release became available https://bugzilla.redhat.com/show_bug.cgi?id=2166311, and so on.


Note You need to log in before you can comment on or make changes to this bug.