From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Rical Jasan Newsgroups: gmane.comp.lib.glibc.alpha Subject: Re: Bugzilla: editbugs privs Date: Thu, 22 Feb 2018 05:48:17 -0800 Message-ID: References: <6bef99df-3cf6-4632-5d7d-dc9dc4c559ca@redhat.com> <2425cbd1-8eda-b15c-634e-c632dcdbffeb@pacific.net> <95ac8c98-2ca2-50d3-4e36-06e5cc3499e9@redhat.com> <76b984d5-711e-e064-6453-abcb102b1023@redhat.com> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Trace: blaine.gmane.org 1519307224 27795 195.159.176.226 (22 Feb 2018 13:47:04 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Thu, 22 Feb 2018 13:47:04 +0000 (UTC) User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 To: Florian Weimer , Carlos O'Donell , libc-alpha Original-X-From: libc-alpha-return-90487-glibc-alpha=m.gmane.org@sourceware.org Thu Feb 22 14:47:00 2018 Return-path: Envelope-to: glibc-alpha@blaine.gmane.org DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:subject:to:references:from:message-id:date :mime-version:in-reply-to:content-type :content-transfer-encoding; q=dns; s=default; b=ytVeryeE9sjkkydN 4K6UrksSbW3UMHr4yGLI7SnA1t5MhbcpW8zbew5hPnCu1ERyuUwVbYQKJiNwjrKN sfiK4fPMQCQ4aFQMhLe23wW/Pp11ZIb+AFjPmPNy8jRxS3ykqJHBp5BuGo5sASmM fe8l08uuaxf1kTkc7nuftlnfL5k= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:subject:to:references:from:message-id:date :mime-version:in-reply-to:content-type :content-transfer-encoding; s=default; bh=3SNbCnUb8OPv+2xLyQbTOf 7OZYw=; b=DBv7WKHnb5SRYKATCzV9KlR1Ft4AFUHz+wOEPxjYRPBbFNsZakSKn7 FNwQM5hD6KftLe99ZSuM0elTmWrGXGppeBe7G/SLX9Vjig9K9ZXkjFB79PPhEGy8 R5tKWCYSDlHaSzvBjkyMExSbDurT6Q4FFYY2UNWwyUbU2bsLre6mc= Mailing-List: contact libc-alpha-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Original-Sender: libc-alpha-owner@sourceware.org Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=BAYES_00,SPF_PASS,TIME_LIMIT_EXCEEDED,T_RP_MATCHES_RCVD autolearn=unavailable version=3.3.2 spammy=HContent-Transfer-Encoding:8bit X-HELO: smtp.pacific.net In-Reply-To: <76b984d5-711e-e064-6453-abcb102b1023@redhat.com> Xref: news.gmane.org gmane.comp.lib.glibc.alpha:82819 Archived-At: Received: from server1.sourceware.org ([209.132.180.131] helo=sourceware.org) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eorD8-0006aP-Lh for glibc-alpha@blaine.gmane.org; Thu, 22 Feb 2018 14:46:59 +0100 Received: (qmail 42221 invoked by alias); 22 Feb 2018 13:49:00 -0000 Received: (qmail 42106 invoked by uid 89); 22 Feb 2018 13:48:46 -0000 On 02/22/2018 04:14 AM, Florian Weimer wrote: > On 02/22/2018 10:13 AM, Carlos O'Donell wrote: >> On 02/19/2018 05:42 PM, Rical Jasan wrote: >>> On 02/19/2018 03:04 AM, Florian Weimer wrote: >>>> On 02/19/2018 11:22 AM, Rical Jasan wrote: >>>>> May I be added to the editbugs group in Bugzilla? [0]  I'm trying to >>>>> close BZ #6889, but it doesn't look like there is very much I can do. >>>> >>>> Please check.  I think I have updated your account. >>> >>> That did the trick, thanks! >>> >>> OOC, is there anything in particular I should be saying in a closing >>> comment?  It feels weird to just write, "Fixed."  I get not wanting >>> empty comments, but I guess there's no (visibly) tracking changes of >>> state otherwise? >> >> Often we say "Fixed in X.Y" as a simple way of making it doubly >> clear when it was fixed and to remind oneself to set the milestone :-) > > Sure, but I think the real reason is that Bugzilla requires something in > that field.  Maybe we should just ask for a configuration change to drop > that requirement? Is there otherwise a visible history of the status changes, though? Nice behaviour IMO would be if it auto-generated a "Marked as RESOLVED FIXED by Some Dev." comment if the status changed but the comment was empty, but if you couldn't follow status changes because no comment was generated, that'd be worse than the current situation, which after I thought about it for a bit is why I asked what I should say instead of why I have to write something. :) Rical