unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefan@marxist.se>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Our use of the "fixed" tag in debbugs
Date: Tue, 5 Oct 2021 15:44:08 -0400	[thread overview]
Message-ID: <CADwFkmkVEftqLBX7s9FY5SpsGn+j7RPz6oLbbmy8zv3xRwt=ug@mail.gmail.com> (raw)
In-Reply-To: <83v92b2stf.fsf@gnu.org>

Eli Zaretskii <eliz@gnu.org> writes:

>> Currently, bugs are unfortunately just left open and untagged, which
>> means that it can take a long time before someone goes back, tediously
>> re-reads everything, and then closes it.  Using this tag more often
>> could save quite a bit of time, I hope.
>
> Tagging is tedious: you need to BCC the control address, you need to
> type the line without making a mistake, etc.  It's so much easier to
> just close the bug.

Indeed, it's a hassle.  Perhaps it would help to have a command for this
in `message-mode' much like `debbugs-gnu-make-control-message'?  Or
perhaps such a thing already exist?

> I'm not sure I understand what will tagging as "fixed" without closing
> will gain us, can you explain?

Tagging is not better than closing.  It is an alternative, if we don't
yet feel confident enough to close it.

Like Glenn, I would urge people to close bugs as well.  Don't think
twice, just do it.  We have thirty days to change our mind before it is
archived.

I have closed many, many dozens of bugs where the only remaining step
was to close it.  It takes extra time after the fact, since you have to
re-read potentially very long threads, scour our git log to see if this
or that patch was applied, and so on.  And the risk of losing track of
any important information pales in comparison to the effort it takes to
go back and close bugs.  It's not a very effective use of our resources.

Of course, some people will go write Reddit or HN threads about how we
are all horrible people, but that's just par for the course.

> As for closing, as long as people start arguing with us why did we
> close without resolving the way they thought we should, I will leave
> bugs open, because I don't have enough time for these arguments.

I feel your pain.  I'm not sure that there are any easy solutions to
frivolous follow-ups, besides answering very briefly or not at all.

OTOH, this is exactly where adding a tag could be easier; and helps
someone like me to find and close it later.



  reply	other threads:[~2021-10-05 19:44 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-05 17:27 Our use of the "fixed" tag in debbugs Stefan Kangas
2021-10-05 17:52 ` Lars Ingebrigtsen
2021-10-05 17:56   ` Stefan Kangas
2021-10-05 17:57 ` Glenn Morris
2021-10-05 18:12 ` Basil L. Contovounesios
2021-10-05 19:08 ` Eli Zaretskii
2021-10-05 19:44   ` Stefan Kangas [this message]
2021-10-05 21:48     ` Stefan Monnier
2021-10-06  7:44     ` Robert Pluim
2021-10-08 11:21 ` Eli Zaretskii
2021-10-08 11:44   ` Basil L. Contovounesios
2021-10-08 15:41     ` Glenn Morris
2021-10-08 16:00       ` Basil L. Contovounesios
2021-10-08 17:16         ` Stefan Kangas

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CADwFkmkVEftqLBX7s9FY5SpsGn+j7RPz6oLbbmy8zv3xRwt=ug@mail.gmail.com' \
    --to=stefan@marxist.se \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).