From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Kangas Newsgroups: gmane.emacs.devel Subject: Re: Our use of the "fixed" tag in debbugs Date: Tue, 5 Oct 2021 15:44:08 -0400 Message-ID: References: <83v92b2stf.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="36433"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue Oct 05 21:45:09 2021 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mXqNA-00096O-5j for ged-emacs-devel@m.gmane-mx.org; Tue, 05 Oct 2021 21:45:08 +0200 Original-Received: from localhost ([::1]:59692 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mXqN3-000100-Up for ged-emacs-devel@m.gmane-mx.org; Tue, 05 Oct 2021 15:45:01 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:47090) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mXqMG-0000Hf-A7 for emacs-devel@gnu.org; Tue, 05 Oct 2021 15:44:12 -0400 Original-Received: from mail-pj1-f51.google.com ([209.85.216.51]:42941) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1mXqME-0004wK-P2; Tue, 05 Oct 2021 15:44:12 -0400 Original-Received: by mail-pj1-f51.google.com with SMTP id rm6-20020a17090b3ec600b0019ece2bdd20so489364pjb.1; Tue, 05 Oct 2021 12:44:09 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:in-reply-to:references:mime-version:date :message-id:subject:to:cc; bh=xUcT1l7BymnWoHMNYDvEsPZaWu0WDozZyxpd/tj651M=; b=IMdGpB91f3e1n2Gs4LLmplkrBQQYOcxWZsLdY2iHrb17MfB642chTV/PYtT9SzCo2r sWNWQs2IOAtkdwQHTlE2Ynwt1mGC+qmr0vDtA/GnVRsjrYQip41Ud209HTCS5J6WPyQm z+8/eNgCVa9kClDK4GTEEzjjCofpzcB3rsh4zC6nfVEZo1opTplhjlbGiE865RpmR01+ +evE7gViUjdbM0+mzgqo70TqV0GRwFBP98cQk+MgA3a8jhSh19FENbn5xpPOMXl2GoCa AQ/x5KNk7e+L1v5UsINic1CysX5OxT82cTtzgh6kGK6rseEfD6cfNRHQ78uqPaEVTETK jwhg== X-Gm-Message-State: AOAM530d+G/Lt6xowzmOGtGDyZWoObXPe/mAgJRdn2nlxwO8E9+PnNqI Mm0Sio8nbAG3lILzxOQdHHPDVGjdU71CcHpP0NVTfnN6 X-Google-Smtp-Source: ABdhPJyWdBVucarOLUsytPPnoJJC1ueoHowVdgiCgcWxJzdGC7/lfad6IlfL2Emv5TQhvNNVzMuudekp49lqPqQUc7A= X-Received: by 2002:a17:90a:5583:: with SMTP id c3mr5823148pji.133.1633463048796; Tue, 05 Oct 2021 12:44:08 -0700 (PDT) Original-Received: from 753933720722 named unknown by gmailapi.google.com with HTTPREST; Tue, 5 Oct 2021 15:44:08 -0400 In-Reply-To: <83v92b2stf.fsf@gnu.org> Received-SPF: pass client-ip=209.85.216.51; envelope-from=stefankangas@gmail.com; helo=mail-pj1-f51.google.com X-Spam_score_int: -13 X-Spam_score: -1.4 X-Spam_bar: - X-Spam_report: (-1.4 / 5.0 requ) BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=no autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:276378 Archived-At: Eli Zaretskii 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.