From: Glenn Morris <rgm@gnu.org>
To: Stefan Kangas <stefan@marxist.se>
Cc: emacs-devel@gnu.org
Subject: Re: Our use of the "fixed" tag in debbugs
Date: Tue, 05 Oct 2021 13:57:53 -0400 [thread overview]
Message-ID: <vdv92b4an2.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <CADwFkmmakuz1NpiA5p+9JgM2ZmYxPFZuS7vXihVFQHvzK0_-Ew@mail.gmail.com> (Stefan Kangas's message of "Tue, 5 Oct 2021 13:27:04 -0400")
Stefan Kangas wrote:
> 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.
Personally I think this is a misuse of the tag, which I have
tried to discourage in https://debbugs.gnu.org/47854, and have actually
been meaning to discourage again. :)
I don't know why some Emacs developers use the tag in this way.
> 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.
Personally I wish people would just be more proactive in closing things
when they believe they are fixed. It's easily reversible if needed;
unless someone has used the fixed tag! :)
> 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.
IMO this is just people failing to close a bug, so I don't see that they
would be any more likely to tag it. Unless for some reason people are
afraid of closing things.
But of course having said all that people doing the work (which doesn't
include me) are free to use the system however they find best.
next prev parent reply other threads:[~2021-10-05 17:57 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 [this message]
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=vdv92b4an2.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=stefan@marxist.se \
/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).