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: Stability of core packages (was: Not easy at all to upgrade :core packages like Eglot) Date: Fri, 21 Apr 2023 00:25:55 +0300 Message-ID: References: <87a5zj2vfo.fsf@gmail.com> <87y1muefks.fsf@gmail.com> <834jpifizy.fsf@gnu.org> <83y1mue1qi.fsf@gnu.org> <83sfd2e01f.fsf@gnu.org> <1a5e5837-513b-84d8-3260-cdbf42b71267@gutov.dev> <83sfcz9rf2.fsf@gnu.org> <09a49ab9-ac72-36a9-3e68-9c633710eba7@gutov.dev> <83r0sh8i1q.fsf@gnu.org> <83a5z482e3.fsf@gnu.org> <83sfcu6g1l.fsf@gnu.org> <83a5z2646y.fsf@gnu.org> <453fdbd2-a29c-5ba6-0e16-21fd8f338f10@gutov.dev> <835y9q62er.fsf@gnu.org> <831qke5zar.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="25352"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.10.0 Cc: joaotavora@gmail.com, emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Thu Apr 20 23:26:54 2023 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 1ppbnp-0006OV-IC for ged-emacs-devel@m.gmane-mx.org; Thu, 20 Apr 2023 23:26:54 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ppbn8-0006Nj-3J; Thu, 20 Apr 2023 17:26:10 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ppbn6-0006Na-SS for emacs-devel@gnu.org; Thu, 20 Apr 2023 17:26:09 -0400 Original-Received: from wnew1-smtp.messagingengine.com ([64.147.123.26]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ppbn1-00057M-S4; Thu, 20 Apr 2023 17:26:08 -0400 Original-Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailnew.west.internal (Postfix) with ESMTP id 56A1E2B06703; Thu, 20 Apr 2023 17:25:59 -0400 (EDT) Original-Received: from mailfrontend2 ([10.202.2.163]) by compute2.internal (MEProxy); Thu, 20 Apr 2023 17:25:59 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gutov.dev; h=cc :cc:content-transfer-encoding:content-type:content-type:date :date:from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:sender:subject:subject:to:to; s=fm2; t= 1682025958; x=1682029558; bh=kVg1epnWYRpHmkJPSiTKzgvWNmvlMCeC1em M+yYgEDc=; b=httO0jKdnhpIKBwLC31h5YjBCM9sVS+uYguEU56sL5F8sSK54e4 0pb2QllPfxdRPS6jkgJDRojJbWZ+v54HuIkjmS6CHgi1bmJ4gsmwXOsRQEu3pAK4 6eLFqeHO823Lck/5oBMTDeVmAnmEXaOwY58FCub/6kAOiluB1gsstscafQtUO5ak LmyIzn9pUkKYmirkFJfYyH1H8p0yQUlfN36KPBa/qfzjk5dCmN+ZpKS7Xq+j0wzY Dk9A5bItFSzMO0htkQ0qdA5ZgZhh9+Ay+NJghfKbIKG8S4fVO9354nk/VWT5lAjv Ly2vcropQjnO409Xcd2aT470qrSmPbUdl0A== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:sender:subject:subject:to:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; t= 1682025958; x=1682029558; bh=kVg1epnWYRpHmkJPSiTKzgvWNmvlMCeC1em M+yYgEDc=; b=WEFYD3hyr0C/bhzA7lCEYTVcDnSnJcaiWux6puWzb2hjLE9gh5/ JCPp5iPnKaoT/3osYCAtgSNEWBy2lqUjUj63yWc87W6/0s7RQsOQUiCgsBYY5q/M WpQ8+2f2RthZCUlxDNEwdQvS8qczK0Sex6MuNDwVSrHD31vaHQ4ZKzDFmAdeJX6L a0cm+gQHuYcxa8QjxJMFkB/HEb85o2tchHqtTuzX6memurM0qsxvonWlBx0vzXBz lf1Lt1Rrwya6LYiKz1FCuvcnX9qwWQ2pXPy9qoJgJ7uWAAPOe+GQOZk9Sz/IjsOi 5Hruo8BEeHyCzcjylc43OWszxpLM96jXGiA== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrfedtvddgudeitdcutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpefkffggfgfuvfevfhfhjggtgfesthejredttdefjeenucfhrhhomhepffhm ihhtrhihucfiuhhtohhvuceoughmihhtrhihsehguhhtohhvrdguvghvqeenucggtffrrg htthgvrhhnpeeigfetveehveevffehledtueekieeikeeufeegudfgfeeghfdulefgfeev ledvveenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpe gumhhithhrhiesghhuthhovhdruggvvh X-ME-Proxy: Feedback-ID: i0e71465a:Fastmail Original-Received: by mail.messagingengine.com (Postfix) with ESMTPA; Thu, 20 Apr 2023 17:25:57 -0400 (EDT) Content-Language: en-US In-Reply-To: <831qke5zar.fsf@gnu.org> Received-SPF: pass client-ip=64.147.123.26; envelope-from=dmitry@gutov.dev; helo=wnew1-smtp.messagingengine.com X-Spam_score_int: -44 X-Spam_score: -4.5 X-Spam_bar: ---- X-Spam_report: (-4.5 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-1.669, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 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-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:305527 Archived-At: On 20/04/2023 18:49, Eli Zaretskii wrote: >> Date: Thu, 20 Apr 2023 18:30:47 +0300 >> Cc:joaotavora@gmail.com,emacs-devel@gnu.org >> From: Dmitry Gutov >> >> When you say "keeping core packages only on ELPA", what do you mean exactly? > That core packages will be only in elpa.git, not in emacs.git. Then > we'd "bundle" them with Emacs when preparing the release tarballs. Okay then, though I'd call them just "bundled" packages from that point. Since "core" is an ELPA term for packages developed inside emacs.git. That separation could also be considered a win, saving time for some of the developers. Which could make up for the extra overhead with managing stable tags. > I believe this is a long-term plan wrt core packages. It was even > discussed a couple of times here. Note that to do the above, we don't really have to implement this stuff as a feature in Emacs (as a UI in package.el), or in elpa-admin. At least not right away. As long as we've agreed on a principle to choose releases to tag as stable, we could just write those git revision down somewhere (using git tags, or some text file in the Emacs repo, or a text file on a server somewhere, ...). And then use that info when bundling the packages.