From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Gitlab Migration Date: Thu, 02 Sep 2021 15:12:04 +0300 Message-ID: <83lf4fnpm3.fsf@gnu.org> References: <83v93srwsp.fsf@gnu.org> <0ce705ec-3ee1-61fa-c8b8-9864e6e2a65a@yandex.ru> <83pmu0rvp8.fsf@gnu.org> <87sfywc7y3.fsf@dick> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="13686"; mail-complaints-to="usenet@ciao.gmane.io" Cc: dgutov@yandex.ru, danflscr@gmail.com, dick.r.chiang@gmail.com, emacs-devel@gnu.org To: Alexander Adolf Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Thu Sep 02 14:16:04 2021 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mLldU-0003J0-Oi for ged-emacs-devel@m.gmane-mx.org; Thu, 02 Sep 2021 14:16:04 +0200 Original-Received: from localhost ([::1]:43828 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mLldT-0005CL-MD for ged-emacs-devel@m.gmane-mx.org; Thu, 02 Sep 2021 08:16:03 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:56744) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mLlZq-0006tM-Fv for emacs-devel@gnu.org; Thu, 02 Sep 2021 08:12:18 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:58518) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mLlZm-0001K9-Lv; Thu, 02 Sep 2021 08:12:15 -0400 Original-Received: from 84.94.185.95.cable.012.net.il ([84.94.185.95]:2871 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mLlZf-0001le-Mg; Thu, 02 Sep 2021 08:12:14 -0400 In-Reply-To: (message from Alexander Adolf on Thu, 02 Sep 2021 13:06:32 +0200) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 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-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:273702 Archived-At: > From: Alexander Adolf > Cc: emacs-devel@gnu.org, danflscr@gmail.com, Dmitry Gutov > Date: Thu, 02 Sep 2021 13:06:32 +0200 > > Thus, the magic words would seem to be "backwards compatibility", and > "migration path". > > "backwards compatibility" := Everything that works via email now, must > equally work via email with the new system. "Everything" is not a requirement, IMO. It's nice to have, but we do so much with email that requiring nothing to change is too much. There should be a way to get notifications via email about the important stuff, and there should be a way to participate in discussing issues via email, including sending patches. > "migration path" := It must be possible to try out one function on the > new system, whilst still using all other functions via email. Also not necessarily a requirement: it's okay if several functions must be tried together. Nice to have, certainly. > Finally, a remark on issue/bug tracking. I have used a great many > trackers, and debbugs and Bugzilla stand out from the crowd. By a huge > margin. The differentiating feature is blocks/depends-on. Many issue > trackers (including those in the various git hosting platforms) lack > this feature altogether. Those trackers who have it, often provide a > limited flavour, e.g. limiting it to one level (i.e. a bug that blocks > another bug, can itself not be blocked by other bugs), or make it > awkward to use (e.g. you have to create a new bug as a subtask of > an existing one, and existing bugs cannot be made into subtasks any more > once created). Well, I agree that this is a good feature, but we don't use it too much here. So it is not high on my list of important features that I'd consider as blocking the migration. > Hence my plea: debbugs ought to remain part of whatever any new system > might be. Not if the new platform learns to support blocking, right? Thanks.