From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Dmitry Gutov Newsgroups: gmane.emacs.devel Subject: Re: decision on moving core packages to ELPA; also move to obsolete? Date: Tue, 15 Dec 2020 22:55:21 +0200 Message-ID: <81776be3-2bfe-2d5c-6aae-6d905426e5cf@yandex.ru> References: <86a6ugnopl.fsf@stephe-leake.org> <83im94b17m.fsf@gnu.org> <834kknatxs.fsf@gnu.org> <83sg86apqb.fsf@gnu.org> <865z52oqfp.fsf@stephe-leake.org> <86wnxinbnx.fsf@stephe-leake.org> <83o8iuann7.fsf@gnu.org> <83h7omakyw.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="28415"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0 Cc: stephen_leake@stephe-leake.org, daniele@grinta.net, emacs-devel@gnu.org To: Eli Zaretskii , Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue Dec 15 21:57:09 2020 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 1kpHNa-0007H2-Ho for ged-emacs-devel@m.gmane-mx.org; Tue, 15 Dec 2020 21:57:06 +0100 Original-Received: from localhost ([::1]:34906 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kpHNZ-0007q5-ET for ged-emacs-devel@m.gmane-mx.org; Tue, 15 Dec 2020 15:57:05 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:47982) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kpHM0-0006Bn-Sn for emacs-devel@gnu.org; Tue, 15 Dec 2020 15:55:28 -0500 Original-Received: from mail-wr1-x429.google.com ([2a00:1450:4864:20::429]:41169) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1kpHLz-0007zy-2d; Tue, 15 Dec 2020 15:55:28 -0500 Original-Received: by mail-wr1-x429.google.com with SMTP id a12so21172940wrv.8; Tue, 15 Dec 2020 12:55:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=1ZbRSAn2p2N+K1tTdO883SLvEQNGjZ/iCmKHZFJOKbM=; b=S898oY+J2dsF2pT3pq0wZ4VwMU5ZgJUcvC4PUTaIG6m25vj1PnavlSRejs+alq2OhF G6+Gc8nvbsmQDa5M1l1H2nqXFM7l/EMZwpWwZV8mtx2COaxPPM/H4PcCLKs4+aM6jOa4 v20gyDYlIIAwZHrqFX4E+qvUxESX5xILJov+DPWwGYiGv3bcL0+2qV0u+ZEi/91Gb4Db uRPIhS/ygAFs+8yeIFNRYk4qn11v2g46PVz1N0PclElSBVZcC6Uq3Bk4Zq7UcwKz+YEc 8s7YuMesyqiawbPncQJ4HDrt4K4Pp9PLU7d+6T1jopNSija0oswPP2a8OL8ZD8dtLzgC R/vQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:subject:to:cc:references:from:message-id :date:user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=1ZbRSAn2p2N+K1tTdO883SLvEQNGjZ/iCmKHZFJOKbM=; b=s2Bl381OUhF97lXN1XpLsg4jkOXG68Wg3iJSXfOIAjAF7fpulnOD3mbqVSe45oeB94 C+OuQhNp3h0DTL3zmHOeoQWDF3X4AJ07McsYPkCdM0F7fDyQM82qmP0KBY3AWRA/6tZB AJyRBfkSesFJEV6hgG3H/30ylCm/JXHIIDlnMtS+gPojsIv6/fiy7tRWZQDJ78sSphVm 0GU8bAoAffBf6G0R1banX5UlKooC1tPWuOT1+ku+NK3q5LiMbIWlyRmhniVhiFnt+Y7T PGtdOuHz3/SHc0FIAAYaeYSaLjKZ6G2DPLrtkWwq1FDEpFdJln6LH0js8Uw6nxTMH+Jm KVpw== X-Gm-Message-State: AOAM5318M+/160V0UWuplolFrERQHbPWmB0Flbam8rkAd2yJVQ/Xs/gH ymHXSiXOdhmzak6QjC/l3O3VYmsd803uYw== X-Google-Smtp-Source: ABdhPJxXRy8CM4KlIKNuE9eIpvolD0z+idUFHLwD8fE0GQAByyEEO9TxDbmAx+ZaUi1ftELuiqeoyA== X-Received: by 2002:adf:a50a:: with SMTP id i10mr31808350wrb.123.1608065724651; Tue, 15 Dec 2020 12:55:24 -0800 (PST) Original-Received: from [192.168.0.6] ([46.251.119.176]) by smtp.googlemail.com with ESMTPSA id 34sm39431280wrh.78.2020.12.15.12.55.23 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 15 Dec 2020 12:55:23 -0800 (PST) In-Reply-To: <83h7omakyw.fsf@gnu.org> Content-Language: en-US Received-SPF: pass client-ip=2a00:1450:4864:20::429; envelope-from=raaahh@gmail.com; helo=mail-wr1-x429.google.com X-Spam_score_int: -14 X-Spam_score: -1.5 X-Spam_bar: - X-Spam_report: (-1.5 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=no autolearn_force=no X-Spam_action: no action 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:260925 Archived-At: On 15.12.2020 22:11, Eli Zaretskii wrote: >>> So please describe how you envision the process of building a release >>> tarball under this assumption. E.g., how do I know which version of >>> package A I want to bundle is stable enough to go to a bugfix elease >>> of Emacs? >> >> I'd expect it to work the same as for Org, MH-E, Gnus, you name it. > > What do you mean by "the same as"? Currently, it is not our decision > which Org/MH-E/etc. version will be in what Emacs branch. The > respective developers make that decision and simply push the version > they decided into our repository. > > Once we separate the repositories, the decision will have to be made > by whoever prepares the tarball, and I don't see how he or she could > be equipped to make that decision, nor how the packages are organized > for this modus operandi. Forgive me if that has already been suggested, but how about either: - When making an Emacs X.YZ release, we require that every "external" package has a tag emacs-xyz in its repository, and we pull in and package that version. - In the very same file in Emacs' tree that the repositories with external packages will be listed, we also list the corresponding revisions that will go into the upcoming release. The latter is essentially the "git modules" model, which we can also use. One advantage it has is that the package author forgotten to push a tag for some Emacs release, we're still covered.