unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefan@marxist.se>
To: emacs-devel@gnu.org
Subject: Our use of the "fixed" tag in debbugs
Date: Tue, 5 Oct 2021 13:27:04 -0400	[thread overview]
Message-ID: <CADwFkmmakuz1NpiA5p+9JgM2ZmYxPFZuS7vXihVFQHvzK0_-Ew@mail.gmail.com> (raw)

We currently use the debbugs "fixed" tag almost exclusively in this way:

    tags NNN fixed
    close NNN 29.1
    thanks

This is fine by me, no change needed here.  There is a slight
duplication in that we say that it's fixed twice, but that's minor.

But I note that the developer documentation says that "fixed" actually
means something slightly different:

    This bug is fixed or worked around, but there's still an issue that
    needs to be resolved.

    https://debbugs.gnu.org/Developer.html#tags

I think we could use this meaning of the "fixed" tag more often.  As
with any tag, it allows us to be a bit more granular with the bug status
than the binary "open bug" or "closed bug".

For example, I just tagged Bug#50985 ("Merging gnulib for Emacs 28.1?")
as "fixed".

    https://debbugs.gnu.org/cgi/bugreport.cgi?bug=50985

The idea here is that, yes, the issue is mainly taken care of but let's
wait with closing it until we feel more confident about the fallout.

Using this tag would also make it easier to find later, so that we can
go back and see that everything is taken care of, and then close it.
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.



             reply	other threads:[~2021-10-05 17:27 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-05 17:27 Stefan Kangas [this message]
2021-10-05 17:52 ` Our use of the "fixed" tag in debbugs 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
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=CADwFkmmakuz1NpiA5p+9JgM2ZmYxPFZuS7vXihVFQHvzK0_-Ew@mail.gmail.com \
    --to=stefan@marxist.se \
    --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).