How to connect TW bugzilla to commits?
I've been sent a promising update to something I logged in bugzilla: https://bugzilla.suse.com/show_bug.cgi?id=1183148#c6 (nmbd nmb.service startup delays multi-user.target by 5 seconds) Comment # 6 on bug 1183148 from Samuel Cabrero We have released the update for the systemd unit files. Please reopen if you continue having the problem. Just out of curiosity: is there an procedure for looking up what has been changed? For example, is there a way to connect bug 1183148 to any commits at github or elsewhere? Michael
On 13.04.2021 01:39, Michael Hamilton wrote:
I've been sent a promising update to something I logged in bugzilla:
https://bugzilla.suse.com/show_bug.cgi?id=1183148#c6 (nmbd nmb.service startup delays multi-user.target by 5 seconds) Comment # 6 on bug 1183148 from Samuel Cabrero We have released the update for the systemd unit files. Please reopen if you continue having the problem.
Just out of curiosity: is there an procedure for looking up what has been changed? For example, is there a way to connect bug 1183148 to any commits at github or elsewhere?
Normally package changelog is expected to include bugzilla number, but it is not really enforced in TW and I do not see any changes in TW or SAMBA development repository related to it. Unfortunately at the end it is up to each contributor to correctly document workd that has been done. "We released update" is about the worst possible comment in this case. Neither it is clear who are those "we" (is it upstream? SAMBA development repository? TW repository?) nor when it was released nor how to find it. The best is really OBS request number which many bugzilla developers provide. If bug number is mentioned in request, you also get automatic comment in bugzilla when this request is accepted.
participants (2)
-
Andrei Borzenkov
-
Michael Hamilton