Side note, ... it would be great to use a standard that many groups use for Git commit logs: "Resolves: rhbz#XXXX" I agree with you Dusty this should be technically possible, and it sounds like a neat idea. We have something a little bit like this for RH Ceph Storage but it is not tied into Pagure/fedmsg. - Ken On Wed, Jan 10, 2018 at 12:26 PM, Dusty Mabe <dusty@xxxxxxxxxxxxx> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256 > > > > On 01/10/2018 05:50 AM, Vít Ondruch wrote: >> >> >> Dne 10.1.2018 v 01:09 Dusty Mabe napsal(a): >>> >>> I go to a dist-git repo and find a bug when browsing the source code. >>> I can >>> open a PR to fix it, but what if I don't know how to fix it? I open an >>> issue, right? >>> >>> Except, there's no issue tracker for dist-git pagure repos. That's >>> what bugzilla >>> is for. Now I need to go to bugzilla, find the component, fill out a >>> bug, yada yada. >>> >>> I understand the need for bugzilla and that it's not going away >>> anytime soon, but could >>> we possibly integrate dist-git pagure issue tracking and bugzilla in a >>> way that makes >>> the whole process more seamless for this workflow. We could even use >>> the bugzilla API >>> and display things differently in pagure if we wanted. >>> >>> These are just suggestions. I feel like this can be improved. >>> >>> Dusty >> >> On the overview page, there is "bug reports" link, is this not enough? >> > > That does help but I'm thinking something a little more integrated. For example: > > An issue is filed in dist-git pagure (which is linked to bugzilla, a BZ is automatically > created). Then in a PR in the commit message it says closes #123459 (the BZ #). and then > the issue state changes once merged to "merged pending release". Then once an rpm with that > commit hits stable the issue (BZ 123459) is closed and a comment is added to the issue that > links to the bodhi update that made it to stagble. The issue no longer appears in the > issue tracker. > > Dusty > -----BEGIN PGP SIGNATURE----- > > iQIzBAEBCAAdFiEEPb6zG5c6sV89tRYPMwLb1zlS5nEFAlpWaMsACgkQMwLb1zlS > 5nGapg/+Ki9HXY1Zj7kEb1kmMWh3iN+LmUkMWStGqShZ2oK9qtGKH+kp/PvIRqB2 > AK02eOdRD5A++U6cbVxkETkv3oucfKEbW/q9VrhqnT3Tjjhexc9TU+bEjVTvgoId > A8R5185ZtghHrRcT7VwuBD9+qrWDUcUy8IcA9Gx/NlnKMc2sBYmrLDRo1nMWCLfq > Dl7sylHMZ0OyFKtE7pUquC4om+RfprJrwtTfF22suYdk9dOgwd97gaeDwvIlQqfB > zjOobU+ykdO2ECR20WP/iyOyby7+riTTbuE+07O4bLDKiKtjzPBbBLyzPasO/tQg > /nld570ENfI/CVv/3vOFq881XOxk+WUCplVXYeNlB8uGJY97U9Hy2aLjUqIo/F+N > yfH4ZsYGA8Gua756vqT4lE/X8nHt6q8Y1d/MK5Oh+zgSUXpcWmTHuFQS4SPvRDWf > 2bSoBfL+XXVfItrU2Rqna6Jf4e+xg0wYDClXTuO/iBWmd2LyyBrfRF7eCf/cNWd6 > M4wmowhJ53/MMkjzpCQ1RZlY1PEDRkTsK3KQZ5S5S4tyAmSEXT0b7LIEOFn6jebm > gCWxLVCl60HDJXFPhaclzluMd6s0mNDEX6Ev2kHdxe/btOTxrX5zoqBP66j6Ew8i > 3yp8IQ2SQ+tsr3fAMJ8mc+1W9pnadDdzOEMJMYPORrjIyQNibQo= > =pzIl > -----END PGP SIGNATURE----- > _______________________________________________ > infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx _______________________________________________ infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx
