From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Ihor Radchenko Newsgroups: gmane.emacs.devel Subject: Re: Emacs 29.3 released Date: Tue, 26 Mar 2024 14:38:59 +0000 Message-ID: <87o7b19hx8.fsf@localhost> References: <86edbzyavw.fsf@gnu.org> <87r0fzsbxz.fsf@gmx.de> <86wmprjumv.fsf@gnu.org> <875xxbtmpp.fsf@gmx.de> <86r0fzjs9x.fsf@gnu.org> <87il199y5d.fsf@gmx.de> <865xx9jh3y.fsf@gnu.org> <875xx9f4ol.fsf@gmx.de> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="14385"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Eli Zaretskii , emacs-devel@gnu.org To: Michael Albinus Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue Mar 26 15:39:26 2024 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 1rp7xW-0003TI-AC for ged-emacs-devel@m.gmane-mx.org; Tue, 26 Mar 2024 15:39:26 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1rp7x9-0005B7-QJ; Tue, 26 Mar 2024 10:39:03 -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 1rp7x8-0005Az-7E for emacs-devel@gnu.org; Tue, 26 Mar 2024 10:39:02 -0400 Original-Received: from mout02.posteo.de ([185.67.36.66]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1rp7x5-0003Gi-En for emacs-devel@gnu.org; Tue, 26 Mar 2024 10:39:01 -0400 Original-Received: from submission (posteo.de [185.67.36.169]) by mout02.posteo.de (Postfix) with ESMTPS id E7248240103 for ; Tue, 26 Mar 2024 15:38:55 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1711463935; bh=btjozSG1RQMVJqbx4DV/z2tmXkFzJl7A9Ya23eWFwGE=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version:Content-Type: From; b=Hoh8hPnPWVm6ErwoJNA3+nhsvwqYssQzUJT9Z13jDmT12rdBprc6lQe5TJ1ngF+Fh n3SLCpi8PCjNMJCtqNBv+mwHgoy46cpUOGgEKVPj2DugL5WhwtB9P7ofe5EOOScHf3 lIo5CGG4PTM+aryG090DJxsJbwfLlSdJr/42/9or+FG7nGB1QWKf09BdtkjH7c6RMQ e4sUCSmHbNL3o+XnSwRnnYz8nFExs3t1FWHZNSXyJqsNDAvkKbt3Gs5NYcoJGQVjhv 5TsKcKkSE7rHIrLhP9x2eStyD4LieibDgswkCf8ng6Skm4ha16s/HHTDXUM24sAJes 2KaNbZCm8dMIg== Original-Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4V3sqz0f0gz6tvy; Tue, 26 Mar 2024 15:38:54 +0100 (CET) In-Reply-To: <875xx9f4ol.fsf@gmx.de> Received-SPF: pass client-ip=185.67.36.66; envelope-from=yantar92@posteo.net; helo=mout02.posteo.de X-Spam_score_int: -43 X-Spam_score: -4.4 X-Spam_bar: ---- X-Spam_report: (-4.4 / 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, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 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:317306 Archived-At: Michael Albinus writes: >> Would it be possible to modify the Tramp revision on the release >> branch so that it would not have the "-pre" suffix, and otherwise >> leave intact the procedure by which you collect and merge fixes to the >> release branch? ... > > It would be possible. I could change the Tramp version in the release > branch to the next anticipated release number. So I could change it now > to "2.6.3.29.4". However, I see at least two problems: > > - The Tramp version doesn't guarantee any longer uniqueness. Tramp > 2.6.3.29.4 would differ today and tomorrow. That was the reason to use > such an ambiguous version like 2.6.3-pre. > > - We might run into problems on ELPA. A user sees a builtin version of > Tramp 2.6.3.29.4, but in order to fix something for her there is also > Tramp 2.6.2.9 (let's say). I fear we'll have a hard time to explain, > that 2.6.2.9 is newer than 2.6.3.29.4. May it be an option to follow what Org mode does? We have a stable branch that we periodically tag as a bugfix release (weekly, if there are new commits). Only tagged bugfix releases are merged to Emacs upstream. The same bugfix releases go to ELPA. > (FWIW, I don't understand yet why 29.3 was such an emergency that it was > released w/o any warning in advance.) CVE. -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at . Support Org development at , or support my work at