From: Michael Albinus <michael.albinus@gmx.de>
To: Brett Viren <bv@bnl.gov>
Cc: emacs-orgmode@gnu.org
Subject: Re: Org mode issue tracker
Date: Wed, 02 Oct 2013 14:38:09 +0200 [thread overview]
Message-ID: <8738oju9u6.fsf@gmx.de> (raw)
In-Reply-To: <ir4siwrwuk1.fsf@lycastus.phy.bnl.gov> (Brett Viren's message of "Thu, 26 Sep 2013 10:01:50 -0400")
Brett Viren <bv@bnl.gov> writes:
> Hi,
Hi Brett,
>> * TODO Subject <timestamp> :emacs_ver:org_ver:org_module:
> ...
>> Emacs version ends up as a tag:
>>
>> * TODO ..... :24.3:
>
> Or, if I add an Org version:
>
> * TODO ..... :24.3:8.0.3:
>
> These bare numbers seem a bit too anonymous to me. I think it's
> unlikely that Org will reach versions in the 20's anytime soon so
> collision won't happen for a while but eventually (hackers willing!) it
> will.
>
> So, I suggest simply qualifying the versions like:
>
> * TODO ..... :emacs_24.3:org_8.0.3:
From the metadata retrieved from debbugs.gnu.org, we have just a list of
version strings. There is no indication about the meaning:
(found_versions "24.3")
One could teach people to use also package names but mere version
numbers, but that's up to the package maintainer's will. So up to now
the strings provided by found_versions will be used as tags, until
there's a better rule for matching.
> I can also see a desire to list other software and their versions that
> might be implicated in the bug being reported. Listing their bare
> versions as tags is, I think, obviously no good. They could just
> include this info in an ad-hoc manner in the body of their report, but
> maybe it would be good to define a property to explicitly list them
> following the same <package>_<version> pattern of the tags.
>
> * TODO ..... :emacs_24.3:org_8.0.3:
> :PROPERTIES:
> :IMPLICATED_SOFTWARE: texlive_2012.20120611-5 beamer_3.10-2
The debbugs server returns also a list like
(found
(item
(key . 24.3)
(value)))
Maybe this could go the direction we want. Obviously, in this example
"key" should be Emacs, and "value" should be 24.3. Then we might also
get something like (if set properly by submitter or maintainer)
(found
(item
(key . "emacs")
(value . 24.3))
(item
(key . "org")
(value . 8.0.3)))
The IMPLICATED_SOFTWARE property proposed by you could be derived from the
(affects)
entry. But I haven't seen ever that somebody uses this attribute. It's
always empty, as shown in this example.
> -Brett.
Best regards, Michael.
next prev parent reply other threads:[~2013-10-02 12:38 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-25 6:43 Org mode issue tracker Carsten Dominik
2013-09-25 7:28 ` Christian Moe
2013-09-25 7:30 ` Carsten Dominik
2013-09-25 7:51 ` Sebastien Vauban
2013-09-25 8:03 ` Carsten Dominik
2013-09-25 9:04 ` Sebastien Vauban
2013-09-25 9:37 ` Carsten Dominik
2013-09-25 8:04 ` Suvayu Ali
2013-09-25 9:06 ` Sebastien Vauban
2013-09-25 9:55 ` Michael Albinus
2013-09-25 12:59 ` Sebastien Vauban
2013-09-25 18:29 ` Loyall, David
2013-09-25 18:54 ` Suvayu Ali
2013-09-25 18:56 ` Michael Albinus
2013-09-26 0:21 ` Suvayu Ali
2013-09-26 7:29 ` Sebastien Vauban
2013-09-26 8:22 ` Suvayu Ali
2013-09-26 8:42 ` Michael Brand
2013-09-26 9:52 ` Sebastien Vauban
2013-09-26 9:34 ` Michael Albinus
2013-09-26 12:13 ` Suvayu Ali
2013-09-26 12:21 ` Suvayu Ali
2013-09-26 12:33 ` Michael Albinus
2013-09-27 19:28 ` org-debbugs.el Michael Albinus
2013-09-27 21:50 ` org-debbugs.el Suvayu Ali
2013-10-02 7:46 ` org-debbugs.el Michael Albinus
2013-10-02 10:05 ` org-debbugs.el Suvayu Ali
2013-10-02 11:44 ` org-debbugs.el Michael Albinus
2013-10-02 11:47 ` org-debbugs.el Michael Albinus
2013-10-02 12:33 ` org-debbugs.el Suvayu Ali
2013-10-02 12:33 ` org-debbugs.el Suvayu Ali
2013-10-04 19:19 ` org-debbugs.el Michael Albinus
2013-10-04 19:46 ` org-debbugs.el Suvayu Ali
2013-10-11 8:03 ` org-debbugs.el Michael Albinus
2013-10-11 10:44 ` org-debbugs.el Suvayu Ali
2013-10-11 11:55 ` org-debbugs.el Nicolas Richard
2013-10-11 12:06 ` org-debbugs.el Thorsten Jolitz
2013-10-11 12:09 ` org-debbugs.el Suvayu Ali
2013-10-11 12:11 ` org-debbugs.el Michael Albinus
2013-10-25 11:28 ` org-debbugs.el Michael Albinus
2013-11-05 16:15 ` org-debbugs.el Bastien
2013-11-05 20:03 ` org-debbugs.el Michael Albinus
2013-11-05 23:53 ` org-debbugs.el Bastien
2013-09-26 14:01 ` Org mode issue tracker Brett Viren
2013-10-02 12:38 ` Michael Albinus [this message]
2013-09-25 8:56 ` Carsten Dominik
2013-09-25 18:29 ` Sebastien Vauban
2013-09-25 22:27 ` Bastien
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8738oju9u6.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=bv@bnl.gov \
--cc=emacs-orgmode@gnu.org \
/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/org-mode.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).