From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: Why Emacs needs a modern bug tracker Date: Sun, 06 Jan 2008 15:15:00 -0500 Message-ID: References: <20080104164454.0A4BD830697@snark.thyrsus.com> <20080104232514.GB2735@muc.de> <20080105122310.GB3014@muc.de> <478010B6.2030200@gmail.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1199650511 23843 80.91.229.12 (6 Jan 2008 20:15:11 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 6 Jan 2008 20:15:11 +0000 (UTC) Cc: emacs-devel@gnu.org To: =?iso-8859-1?Q?=D3scar?= Fuentes Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Jan 06 21:15:32 2008 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1JBbu7-0001Iz-Va for ged-emacs-devel@m.gmane.org; Sun, 06 Jan 2008 21:15:32 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JBbtk-0003ps-Ve for ged-emacs-devel@m.gmane.org; Sun, 06 Jan 2008 15:15:09 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JBbtg-0003p7-FN for emacs-devel@gnu.org; Sun, 06 Jan 2008 15:15:04 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JBbte-0003om-VP for emacs-devel@gnu.org; Sun, 06 Jan 2008 15:15:04 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JBbte-0003oj-RP for emacs-devel@gnu.org; Sun, 06 Jan 2008 15:15:02 -0500 Original-Received: from ironport2-out.pppoe.ca ([206.248.154.182]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1JBbte-0002vT-NM for emacs-devel@gnu.org; Sun, 06 Jan 2008 15:15:02 -0500 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ao8CAB/FgEfO+K+E/2dsb2JhbACmdg X-IronPort-AV: E=Sophos;i="4.24,250,1196658000"; d="scan'208";a="12341567" Original-Received: from smtp.pppoe.ca ([65.39.196.238]) by ironport2-out.pppoe.ca with ESMTP; 06 Jan 2008 15:15:01 -0500 Original-Received: from pastel.home ([206.248.175.132]) by smtp.pppoe.ca (Internet Mail Server v1.0) with ESMTP id MVV47601; Sun, 06 Jan 2008 15:15:01 -0500 Original-Received: by pastel.home (Postfix, from userid 20848) id CF5BE7F7C; Sun, 6 Jan 2008 15:15:00 -0500 (EST) In-Reply-To: (=?iso-8859-1?Q?=22=D3scar?= Fuentes"'s message of "Sun, 06 Jan 2008 18:13:20 +0100") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.50 (gnu/linux) X-detected-kernel: by monty-python.gnu.org: Genre and OS details not recognized. X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:86380 Archived-At: >>>>> I was thinking about this possibility and concluded that it is not >>>>> possible to build a decent bug-tracking system using only a VCS. The >>>>> reason is the importance of the user interface, which must be open to >>>>> everybody, not only for the committers, as PROBLEMS and TODO are now, >>>>> thus effectively dissuading possible contributions from the outside. >>>> OK, VCS access IN ADDITION TO web access. How about that? >>> >>> Others just proposed such a system. I'm skeptical about it. So far, it >>> seems quite limiting and for a good reason: >> >> I do not get your point here. Can you explain why you are skeptical >> and why you think it would be limiting in another way? > Because of this: >>>>> Furthermore, a bug-tracking system needs a database and a VCS is not >>>>> good at that. > A VCS provides a filesystem to work on, not a database. > A bug tracker based on a VCS wouldn't provide more that what we can > achieve now with FOR-RELEASE, TODO, etc. I think you're confusing things a little: the database should be inside a file like TODO which is itself managed via a VCS (actually the file needs to be alongside the rest of the code). This way when we merge the unicode branch into the trunk (for instance), the unicode-branch bugs database will "automatically" get merged into the trunk's bugs database. Stefan