From: Michael Albinus <michael.albinus@gmx.de>
To: Tino Calancha <tino.calancha@gmail.com>
Cc: larsi@gnus.org, emacs-devel@gnu.org
Subject: Re: debbugs-gnu-bugs shows unanswered bugs as handled
Date: Sun, 05 Jun 2016 17:29:20 +0200 [thread overview]
Message-ID: <87d1nv1wof.fsf@gmx.de> (raw)
In-Reply-To: <alpine.LRH.2.20.1606052302590.13606@calancha-ilc.kek.jp> (Tino Calancha's message of "Sun, 5 Jun 2016 23:50:34 +0900 (JST)")
Tino Calancha <tino.calancha@gmail.com> writes:
> Hi Michael,
Hi Tino,
> Unfortunately, i don't see that the field 'owner gets always a value.
> AFAICT it never gets a value. Why this field is not always updated?
>
> If each time that one maintainer answer one bug, the field
> 'owner would be updated (adding get his/her name if still not there)
> then it would be trivial to classify one bug as 'new or 'handled.
The idea of `owner' is different. It is not set automatically. But
everybody is allowd to declare herself as owner of a bug, by sending an
appropriate control message to the debbugs server, see the section "3.3
Control Messages" of the debbugs user guide. With this a developer
declares publicly, that she is working on the bug, and nobody else needs
to care about.
This would be a valuable information. Sadly, as you have observed, this
is used rarely. I have done it for some few bugs (4604,6850,8860).
> Wouldn't be ok if 'owner gets as value one list of maintaneirs?
> I would suggest the value of 'owner to be all the maintainers
> answering such bug.
No, because if somebody is answering to a bug it doesn't mean she feels
responsible for that bug.
> Regards,
>
> Tino
Best regards, Michael.
next prev parent reply other threads:[~2016-06-05 15:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-04 4:10 debbugs-gnu-bugs shows unanswered bugs as handled Tino Calancha
2016-06-04 8:25 ` Michael Albinus
2016-06-05 14:50 ` Tino Calancha
2016-06-05 15:29 ` Michael Albinus [this message]
2016-06-08 13:29 ` Tino Calancha
2016-06-11 17:56 ` Michael Albinus
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d1nv1wof.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.org \
--cc=tino.calancha@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.