From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Alex Gramiak Newsgroups: gmane.emacs.devel Subject: Re: [RFE] Migration to gitlab Date: Fri, 10 May 2019 16:23:03 -0600 Message-ID: <87lfzehrug.fsf@gmail.com> References: <1552789070.5272.1@yandex.ru> <87imwhmmt8.fsf@gmail.com> <87y347g1l3.fsf@iotcl.com> <9ac21e82-8e47-f9b5-f88d-23c0c56946d1@yandex.ru> <87pnpc1lby.fsf@iotcl.com> <83zhoezdqc.fsf@gnu.org> <87imuivfcr.fsf@iotcl.com> <83k1eyfxls.fsf@gnu.org> <17D21056-10B2-4813-AE90-9B2706936CE9@icloud.com> <83imuifqjc.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="241519"; mail-complaints-to="usenet@blaine.gmane.org" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.2 (gnu/linux) Cc: toon@iotcl.com, dgutov@yandex.ru, monnier@iro.umontreal.ca, emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat May 11 00:23:13 2019 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hPDv4-0010ag-Mq for ged-emacs-devel@m.gmane.org; Sat, 11 May 2019 00:23:10 +0200 Original-Received: from localhost ([127.0.0.1]:50793 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hPDv3-0002b8-LR for ged-emacs-devel@m.gmane.org; Fri, 10 May 2019 18:23:09 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:56666) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hPDuy-0002b2-52 for emacs-devel@gnu.org; Fri, 10 May 2019 18:23:05 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hPDux-00040b-9O for emacs-devel@gnu.org; Fri, 10 May 2019 18:23:04 -0400 Original-Received: from mail-pg1-x530.google.com ([2607:f8b0:4864:20::530]:37031) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1hPDux-0003zi-2w; Fri, 10 May 2019 18:23:03 -0400 Original-Received: by mail-pg1-x530.google.com with SMTP id e6so3645347pgc.4; Fri, 10 May 2019 15:23:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:subject:references:date:in-reply-to:message-id :user-agent:mime-version; bh=N22T5hFxD6sVsBEVecfMfmnDhkZqS9b9jkKbNaZ58p0=; b=ACRUi8ponDWw0kFoHUlHjAbm61GiEcPen71VeZ4dw76iEeeAYiaRibBm5EzEySO5pT vvv10L4o/hi10KRDHT+IgM/EeciJw1nwNDa8eEYNTlA9i/hWZxFUPr1eHG60zdHY4uox GfuUS40K6hRXCZIy5dQF0hIZbk9QkhZxANZxrwzANe5682C6Arr8RPgYGt1WKsF7ba6e mXakEtgDepbaALD51zBv5xI2o46xqgPFMroI+yluSWMm0q+WnfQkZky0+IJ4x+s6lTno 0fiJU0CoLK6dm6RfJf1Qz4QtgWlOcwg5+Snv5hACJzuT7gROMYvgeQcyRZl+4HdFRccz xnsw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:references:date:in-reply-to :message-id:user-agent:mime-version; bh=N22T5hFxD6sVsBEVecfMfmnDhkZqS9b9jkKbNaZ58p0=; b=aWVYAgmx5cPlOedukgD3p8EIA+KZUdVEbKgHBlAeoW8Re+6dupTSz9T6TLuqGWxsL4 o2apeCK7SEgndUGBCwXa1r7TyUiiSVR/ZoIQTD08tKgYRG0DO94jCm4EWYV1DqWf/crz oEUoxcIKWIS0JmYhRQqK8vaC1+WWwgYyVSKgy/ZHLJBgCwlC/c4f7/EPCWgjOBmomKhE xpZE3/n3lB8pPVwzhu+NclsAE+N0JppCDJkrKFYDk5FCgiJuQ/2+dhF7crN98YJMBbUq JaUByhm9/lvK76oJRpdVeDmFaSvfDakEJTPCT5a2zJ+C3NFFIxYWfWwipwq8eNUfszxQ vFZQ== X-Gm-Message-State: APjAAAWgLs+s9DGHfvrJMm8W3Q3CedjxTATT3Rfnf9tYI+GfZjIyjDeV WWXeEP1urSOv/+q0jh0Cq+w= X-Google-Smtp-Source: APXvYqwPtdSCxlSIQ2pkNVo8jb0MOL+U+paFtmTNG8+dUGSYscz1LkDXP658HX9eaGAUa+373PPuKg== X-Received: by 2002:a63:295:: with SMTP id 143mr16580533pgc.279.1557526981614; Fri, 10 May 2019 15:23:01 -0700 (PDT) Original-Received: from lylat ([2604:3d09:e37f:1500:1a72:4878:e793:7302]) by smtp.gmail.com with ESMTPSA id g72sm16887773pfg.63.2019.05.10.15.22.59 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Fri, 10 May 2019 15:23:00 -0700 (PDT) In-Reply-To: <83imuifqjc.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 10 May 2019 15:21:59 +0300") X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 2607:f8b0:4864:20::530 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:236398 Archived-At: Eli Zaretskii writes: > My point was that an absolute majority of Emacs issues don't have a > patch attached. They describe a problem, and most of the reports > don't even include a detailed analysis of the problem and its root > cause. A large part of discussing an issue is devoted to > understanding the issue and then finding its cause. Patches appear > only after all that. > > So we must have a good support for a workflow that doesn't include any > pull/merge request at its beginning, maybe even never. Gitlab et al. would provide that, IMO. When there's no PR/MR at the beginning, the topic is submitted as an "Issue" and given a unique issue number. However, patches aren't submitted to the issue: rather, a new PR/MR is created, given a unique MR number, and is linked with the relevant issue(s). When the PR/MR is merged, any linked issues are closed. This means that the discussion gets separated into two parts: the discussion about the issue/problem (kept in the "Issues" category), and the discussion about the patch/solution (kept in the "Merge Requests" category).