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: debbugs tracker builds character Date: Thu, 21 Jul 2016 11:38:09 -0400 Message-ID: References: <83vb50wxhv.fsf@gnu.org> <87y49vz4cg.fsf@acer.localhost.com> <87twg2g86g.fsf@lifelogs.com> <83eg76n5h5.fsf@gnu.org> <87y45eeoor.fsf@lifelogs.com> <577D42BB.1020500@cs.ucla.edu> <87oa694rfw.fsf@russet.org.uk> <837fcxlbay.fsf@gnu.org> <87lh1d2wg5.fsf@russet.org.uk> <83eg75jk5h.fsf@gnu.org> <87lh1cb6p0.fsf@lifelogs.com> <87oa5sa176.fsf_-_@lifelogs.com> <874m7kmkcm.fsf@gmx.de> <871t2o6t94.fsf@gmx.de> <87wpkf6pup.fsf@lifelogs.com> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1469115551 20817 80.91.229.3 (21 Jul 2016 15:39:11 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 21 Jul 2016 15:39:11 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Jul 21 17:39:04 2016 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1bQG3z-0003ta-Op for ged-emacs-devel@m.gmane.org; Thu, 21 Jul 2016 17:39:03 +0200 Original-Received: from localhost ([::1]:41591 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bQG3z-0002jn-1W for ged-emacs-devel@m.gmane.org; Thu, 21 Jul 2016 11:39:03 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:59785) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bQG3U-0002ii-FQ for emacs-devel@gnu.org; Thu, 21 Jul 2016 11:38:33 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bQG3Q-0003k7-8o for emacs-devel@gnu.org; Thu, 21 Jul 2016 11:38:31 -0400 Original-Received: from plane.gmane.org ([80.91.229.3]:37664) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bQG3Q-0003k2-1L for emacs-devel@gnu.org; Thu, 21 Jul 2016 11:38:28 -0400 Original-Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1bQG3G-0003Ol-JX for emacs-devel@gnu.org; Thu, 21 Jul 2016 17:38:18 +0200 Original-Received: from 69-165-156-121.dsl.teksavvy.com ([69.165.156.121]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 21 Jul 2016 17:38:18 +0200 Original-Received: from monnier by 69-165-156-121.dsl.teksavvy.com with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 21 Jul 2016 17:38:18 +0200 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 30 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 69-165-156-121.dsl.teksavvy.com User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.1.50 (gnu/linux) Cancel-Lock: sha1:4pyaNbURI3hgPZ4AOOgCoIh9T+o= X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 80.91.229.3 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:205972 Archived-At: SM> I think I'm starting to see what you mean. You're talking about a tight SM> integration where a pull-request is also itself an issue, so the comments SM> can be directly on the patch itself. As opposed to having issues and SM> pull-request be two separate things that can refer to each other via SM> an indirection. > Yes. Actually Github has both of these right now. When pull requests are > not true issues, they tend to be associated with issues: sometimes > 1-to-N and sometimes N-to-1. People have different workflows, so it's > good to have flexibility built into the model. Sorry if this seems > ambivalent; it's really a degree of creative freedom that users > appreciate. So, we could start by setting up a Gitlab or Kallithea instance for Emacs and use it for pull-requests, while we keep using Debbugs for issue tracking. This lets us move forward on the pull-request and code-review front without having to solve the "issue" of switching to another bug-tracker. EA> A suggestion from a part-time package maintainer: make EA> `report-emacs-bug' prompt for a package, and offer the results of EA> `featurep' as completion. If the user picks a package that only exists EA> in ELPA, email the package maintainer with the bug report. > That's a really good suggestion, regardless of the underlying bug tracker. I also like this idea. Patches welcome, Stefan