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: Thu, 20 Apr 2023 17:22:03 +0300 Message-ID: <453fdbd2-a29c-5ba6-0e16-21fd8f338f10@gutov.dev> References: <87a5zj2vfo.fsf@gmail.com> <87wn2fk47y.fsf@posteo.net> <83sfd2g2ek.fsf@gnu.org> <875y9yfxrr.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> 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="15192"; 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 16:22:32 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 1ppVB9-0003cz-Nv for ged-emacs-devel@m.gmane-mx.org; Thu, 20 Apr 2023 16:22:32 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ppVAw-0005OY-Px; Thu, 20 Apr 2023 10:22:18 -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 1ppVAs-0005O3-Ok for emacs-devel@gnu.org; Thu, 20 Apr 2023 10:22:17 -0400 Original-Received: from wnew2-smtp.messagingengine.com ([64.147.123.27]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ppVAq-0005Mn-LC; Thu, 20 Apr 2023 10:22:14 -0400 Original-Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailnew.west.internal (Postfix) with ESMTP id 8B3712B066AD; Thu, 20 Apr 2023 10:22:08 -0400 (EDT) Original-Received: from mailfrontend2 ([10.202.2.163]) by compute3.internal (MEProxy); Thu, 20 Apr 2023 10:22:08 -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= 1682000528; x=1682004128; bh=DzpQ1DA8ai30teMf5cDxokaiT6heqnU5FFm Bp5x70S4=; b=EGXIr/SJdf9gpfDYkaW5tzuE2lRdGodoURjWw63xeTYHHkT8P0z 2ckML6Um2vu+bLliWRAmkGUNtHnmVPdKBedX0pXkO3ud8mQ7R5zVbDkWcHkhxZtc ATq0R9xcLlhGMQw3jGVpjyaoV1eRHWnk+k0Der85WAEgpskuf085wTU5/6qOX60k YAxHUEo+VrUxrN5ooFRY4OYOcg5QM2Jkx7GeEcVqw5ql/Znzt2eFQGQjFcxXO48F 7JffVNhViVWAx+9C16R5cKg9hVHxCepkxjqHXpAftYOnqTl2HXgO7DtX95Kvi00p 7+zj57l8X0ae6W9KuDPYLQW6kYmmhFJ7jGw== 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= 1682000528; x=1682004128; bh=DzpQ1DA8ai30teMf5cDxokaiT6heqnU5FFm Bp5x70S4=; b=Mxdf3eM5SGC/WQOsOICrKCpctWzo99WQq+XTAYVb8KDYdJkhjVt cO/wWa0yKw92OJpnDn6QaMtOeQCHOu/5n2M8tTS4mBtIIzRNJruY+/zNp/oSqYKt eJTj3EsEPdQ7IvCd3m5tArLmRNfEozrB4MMNU+DCYIfEI0WjoePJwHAcIRA/8DGr 2zHJCk8AUn/W9EJVKTK75MpYbTifHmakdc8o8ck9hBfH9n4r8nnv3EN+ueEnaF74 VV6ov8Yb5R4kKMkxZEvoIXiGdau01s61SGe/xofTEZDIXoLAgkxzcn3bVfA6i3dz OvLjQPWaRvbWBcCBZfmBuIva0cyVDFdbaAw== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrfedtvddgjeegucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepkfffgggfuffvvehfhfgjtgfgsehtjeertddtfeejnecuhfhrohhmpeffmhhi thhrhicuifhuthhovhcuoegumhhithhrhiesghhuthhovhdruggvvheqnecuggftrfgrth htvghrnhepiefgteevheevveffheeltdeukeeiieekueefgedugfefgefhudelgfefveel vdevnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepug hmihhtrhihsehguhhtohhvrdguvghv X-ME-Proxy: Feedback-ID: i0e71465a:Fastmail Original-Received: by mail.messagingengine.com (Postfix) with ESMTPA; Thu, 20 Apr 2023 10:22:05 -0400 (EDT) Content-Language: en-US In-Reply-To: <83a5z2646y.fsf@gnu.org> Received-SPF: pass client-ip=64.147.123.27; envelope-from=dmitry@gutov.dev; helo=wnew2-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:305512 Archived-At: On 20/04/2023 17:03, Eli Zaretskii wrote: > Perhaps there's some kind of misunderstanding here. To me, declaring > a version of a package "stable" just means some label in its metadata, > which is exposed to package.el and to the users. So when the package > developer decides that "N weeks have passed", he or she will add that > label, thus making the corresponding version be considered "stable". > Next time users check for updates they will see that, and could then > upgrade to the "next stable" version if they so desire. > > IOW, the version on ELPA that wasn't "stable" before, and was used for > testing, now becomes "stable". Okay. That can work if: - We're able to force at least some older versions of the package to stay around in the repository. And we'll probably need some new UI in package.el to be able to choose among the versions. - We're able to retroactively add some metadata to already published versions, like calling some older one "stable" after some time has passed. > Users of Emacs 29 that need a newer Eglot don't need to stay with the > version we shipped. First, if the machinery to promote Eglot versions > to "stable" status is in place, bug-fix 29.x releases could have newer > versions of Eglot bundled with them; our rate of putting out bug-fix > releases is much higher than once every 2 years. That's fair. > Users who cannot > wait until the next bug-fix release, but still want stabil > > ity, will be > able to upgrade their Eglot to a newer version, provided that we mark > some newer version on ELPA "stable" after "N weeks" or so. Finally, > users who want newer Eglot badly and are willing to sacrifice some > stability will update to the latest-and-greatest version on ELPA, even > if it is not "stable" yet. So we seem to agree that the ability to upgrade is important as well. Whether we're able to transition to a new system with stability tags, etc, is yet to be seen. > So I don't see how this can lose, if we indeed have the above system, > or something like it, in place. The main downsides of this are probably obvious: - The development work required. - The additional ongoing package maintenance work that is implied by this design. Whether it's really worth it in the end, I don't know. E.g. Joao seems to think that additional stable releases for Eglot won't have much of an audience (which seems sensible to me), but Arne's messages seem to indicate a preference for stability. And the larger community seems to be using MELPA quite happily, which is as unstable as it gets. Maybe it won't be used much by Eglot, but Org devs take a liking to it. On my part, I would maybe tag a "stable" release once a year or so.