From mboxrd@z Thu Jan 1 00:00:00 1970 From: Brett Viren Subject: Re: Org mode issue tracker Date: Thu, 26 Sep 2013 10:01:50 -0400 Message-ID: References: <86ioxp2vbb.fsf@somewhere.org> <20130925080403.GS12411@kuru.dyndns-at-home.com> <86siwt1d9c.fsf@somewhere.org> <8738otjkdt.fsf@gmx.de> <871u4czq4t.fsf@gmx.de> <20130926002156.GA13887@kuru.dyndns-at-home.com> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:49618) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VPC9A-0000Ga-B8 for emacs-orgmode@gnu.org; Thu, 26 Sep 2013 10:02:32 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VPC91-0004jS-M0 for emacs-orgmode@gnu.org; Thu, 26 Sep 2013 10:02:24 -0400 Received: from smtpgw.bnl.gov ([2620:10a:0:3::30]:38527 helo=iron4.sec.bnl.local) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VPC91-0004f9-HW for emacs-orgmode@gnu.org; Thu, 26 Sep 2013 10:02:15 -0400 In-Reply-To: <20130926002156.GA13887@kuru.dyndns-at-home.com> (Suvayu Ali's message of "Thu, 26 Sep 2013 02:21:56 +0200") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Suvayu Ali Cc: emacs-orgmode@gnu.org --=-=-= Content-Type: text/plain Hi, Suvayu Ali writes: > * TODO Subject :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: 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 _ pattern of the tags. * TODO ..... :emacs_24.3:org_8.0.3: :PROPERTIES: :IMPLICATED_SOFTWARE: texlive_2012.20120611-5 beamer_3.10-2 BTW, I think an issue tracker in Org is very interesting. I look forward to seeing how it evolves. -Brett. --=-=-= Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlJEPk4ACgkQEixH2Z0dKCwmuwCeLd8Xhp9PEvv/zunaBgDw/jGz h7sAoJop+xWDCn9xCVRYfsEoYCjGh+eY =hALt -----END PGP SIGNATURE----- --=-=-=--