WANTED: bugzilla help (automated and semi-automated) closing bugs
Jeremy Allison
jra at samba.org
Thu Jun 20 16:29:09 UTC 2019
On Thu, Jun 20, 2019 at 11:22:20AM +0200, Björn JACKE via samba-technical wrote:
> On 2019-06-20 at 06:06 +1200 Andrew Bartlett sent off:
> > 1. push to autobuild
> > 2. wait for autobuild
> > 3. enter git hash and version into gitlab and close
> > 4. enter git hash and version into bugzilla and think about backport
> > 5. do backport
> > 6. get reviews
> > 7. assign to karolin
> > 8. Karolin then pushes to autobuild
> > 9. Karolin then updates bugzilla as pushed
> > 10. Kaorlin then updates bugzilla as in the release and closes.
> >
> > Steps 1-4 and 7-10 are way to manual, and so much falls between the
> > cracks, and when it doesn't, it takes way too much time.
> >
> > I think we should at least try to automate 1-4, so MRs and bugzilla
> > entries close as soon as they are plausibly merged, or we switch to
> > tooling that is joined-up, where this happens out of the box.
> >
> > If the developer really cares about the issue (and the automated
> > process was wrong) they can re-open things of course, but in the
> > meantime things are ready for the next major release.
>
> I go along with this reg. adding such an automation process for new bug
> activities because for currently open bugs with activity the process is
> "reviewable" via the samba-qa mails. I'm happy to help with this also.
>
> My concerns that I had and still have are about the automatic closing of huge
> numbers of existing bug reports, only because the bug number was mentioned in a
> commit message for example. For huge numbers this would not be verifyable.
>
> A good start for anyone to tidy up hir own backyard would maybe be to look over
> hir self-reported and self-assinged bugs and have a look which of thos can be
> obviously closed.
>
> https://bugzilla.samba.org/buglist.cgi?bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailreporter1=1&emailtype1=exact&field0-0-0=bug_status&field0-0-1=reporter&list_id=22179&type0-0-0=notequals&type0-0-1=equals&value0-0-0=UNCONFIRMED&email1=FOO@SAMBA.org
>
> Just replace FOO at SAMBA.ORG with your own bugzilla mail address.
>
> I would also recommend to save this search request for quick and easy future
> use, you can do that by giving it a name like "My Bugs" and press the "Remember
> search" button at the bottom of the search result site. You will then have a
> link "My Bugs" at the bottom of each bugzilla site.
That's a really useful link - thanks a *LOT* ! Saved as "MY BUGS" :-).
More information about the samba-technical
mailing list