On 9/15/21 1:54 PM, Miro Hrončok wrote: > On 15. 09. 21 13:00, Vít Ondruch wrote: >> >> Dne 15. 09. 21 v 12:57 Petr Menšík napsal(a): >>> >>> Hi Sahana, >>> >>> it would be nice, if changelog entry contained bug id we could use >>> to watch the progress. >>> >> >> The commit message should contain reference to the change proposal IMO Yes, something similar to mass rebuilds before new release. They also have URL to details. I think all non-maintainer commits should have some reference to details, why is it done. > > I've never referenced the Bugzilla ID or change proposal when I've > done Python 3.X rebuilds and I have never heard somebody that it > mattered to them. > > Referencing the change in the commit message is actually a good idea > in retrospect. However, referencing a bug ID might create a lot of > noise, we once did that here: > > https://bugzilla.redhat.com/show_bug.cgi?id=1748018 This bug is something I had on mind. But I would expect it would be only used as Depends: field on bugs filled to failed components. I were looking for a bug number to add to block > > People kept associating unrelated EPEL updates with this for months, > as "fedpkg update" or some other clever thing automatically added that > bug ID to them. > Indeed, there were a lot of EPEL builds referencing Fedora bug. If that were done by any existing tool, it should be fixed. I doubt we ever want EPEL builds to directly reference Fedora builds. It might be done in rare cases by a person, but I doubt it should ever be done by any automated tool. Maybe if it had bug cloned to EPEL, it might followed clone with matching product for the build. I think we miss here way to make that bug only related. It might be added to bodhi updates of such builds, but it should not switch state of referenced bug in any way, let alone close it. It should just be clickable link from bodhi update. It should be considered only as indication similar problem had multiple packages. Would such feature make sense also to others? Cheers, Petr -- Petr Menšík Software Engineer Red Hat, http://www.redhat.com/ email: pemensik@xxxxxxxxxx PGP: DFCF908DB7C87E8E529925BC4931CA5B6C9FC5CB _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
