From: Lars Ingebrigtsen <larsi@gnus.org>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: bug#37854 <37854@debbugs.gnu.org>
Subject: bug#37854: 27.0.50; debbugs-gnu doesn't return date bugs were closed
Date: Tue, 22 Oct 2019 11:47:32 +0200 [thread overview]
Message-ID: <87k18xnmbv.fsf@gnus.org> (raw)
In-Reply-To: <87tv81f7o1.fsf_-_@gmx.de> (Michael Albinus's message of "Tue, 22 Oct 2019 11:31:26 +0200")
Michael Albinus <michael.albinus@gmx.de> writes:
> Well, it looks like this close date is not an attribute of the bug, but
> something the database keeps internal for countdown of the 28 days,
> until the bug will be archived. Once archived, this information doesn't
> seem to be available anymore.
Right.
I was also wondering why the charts I made estimate the number of tags
(like "moreinfo"/"patch") too high, but of course I only have what the
data look like now.
So while my charts say that there were 200 open "moreinfo" in, say,
December 2018, there weren't that many. A bug report that got that tag
in later, and was closed later, will be counted as having had that tag
back then.
Would it be possible to include the entire change history in the SOAP
data? That is, the timestamps when tags/severities are added/removed?
That is, is there a "log" of changes applied to a bug that can be
output? If there was, that'd also fix the "closed" date handling
problem.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2019-10-22 9:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <83lftf43hy.fsf@gnu.org>
[not found] ` <877e4zdvgx.fsf@gnus.org>
[not found] ` <83ftjm4o74.fsf@gnu.org>
[not found] ` <877e4ymugu.fsf@gmx.de>
[not found] ` <877e4yqmf9.fsf@gnus.org>
[not found] ` <878spegqbv.fsf@gmx.de>
[not found] ` <8736fmqk3x.fsf@gnus.org>
[not found] ` <874l02gp0q.fsf@gmx.de>
[not found] ` <87y2xep3jm.fsf@gnus.org>
2019-10-22 9:31 ` bug#37854: 27.0.50; debbugs-gnu doesn't return date bugs were closed Michael Albinus
2019-10-22 9:47 ` Lars Ingebrigtsen [this message]
2019-10-24 8:20 ` Michael Albinus
2019-10-24 12:02 ` Lars Ingebrigtsen
2019-10-24 13:56 ` Michael Albinus
2019-10-21 17:12 Lars Ingebrigtsen
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=87k18xnmbv.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=37854@debbugs.gnu.org \
--cc=michael.albinus@gmx.de \
/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).