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 18:01:48 +0000 Message-ID: <87ttks98j7.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> <87o7b19hx8.fsf@localhost> <87zfukevby.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="4343"; 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 19:02:59 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 1rpB8U-0000sP-Ti for ged-emacs-devel@m.gmane-mx.org; Tue, 26 Mar 2024 19:02:59 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1rpB7a-0001DP-5m; Tue, 26 Mar 2024 14:02:02 -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 1rpB7U-0001Cc-L9 for emacs-devel@gnu.org; Tue, 26 Mar 2024 14:01:57 -0400 Original-Received: from mout01.posteo.de ([185.67.36.65]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1rpB7M-0004JP-Gc for emacs-devel@gnu.org; Tue, 26 Mar 2024 14:01:52 -0400 Original-Received: from submission (posteo.de [185.67.36.169]) by mout01.posteo.de (Postfix) with ESMTPS id 4C89624002B for ; Tue, 26 Mar 2024 19:01:46 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1711476106; bh=/MRIlGsjCgiZITv+8TpnHlGW9Mmr48nesc6FXHtbXN8=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version:Content-Type: From; b=q7bZiClBhXBRtcIXDpGAE7cEXnuiM7maodKDsv5HNPIvXK8sngASfpV+1CPwGVXVm zz43lIELy1KJkjWAt70lUan3jUkhTlqBUaiHtBo0ABZApWlN7Q3EnUEGFGvekQlHYi kGHoJyZCU4aLcno0BxnmvsHoq7jFGCDYjCEWGA5gwMv9wg7iKIeA04dXOr6l+XB50R zCH4QxyAlf9s42FfW2JNk7TL23RAw5jP9IyA7VRUqWDqVnqG5uq473xl7vKjzS9oXn kXP5tb5z4kbnK++UdNb9oAhrCQyYVPYtbNA78HIIZoHGJL83WosUBSSCxZp5yKYS9Y WZoFh5CENhK2Q== Original-Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4V3yL13xGWz6tws; Tue, 26 Mar 2024 19:01:45 +0100 (CET) In-Reply-To: <87zfukevby.fsf@gmx.de> Received-SPF: pass client-ip=185.67.36.65; envelope-from=yantar92@posteo.net; helo=mout01.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_H3=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:317312 Archived-At: Michael Albinus writes: >> 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. > > Tramp does something similar on GNU ELPA. It pushes bug fix releases > with a dedicated version. It happens monthly only, submissions to Tramp > happen less frequently. > > However, it doesn't push the same bugfix release to the emacs-29 branch, > because not every bug fix is essential while Emeca is in pretest. I see. So, you effectively have to "bugfix" versions - one with hand-picked commits for Emacs pretest and one with more commits for ELPA. Maybe you can split the versions into Emacs-only and, fuller, proper bugfix. Say, something like Tramp 2.6.2.. and Tramp 2.6.2.. Then, if emacs=1 and elpa=2, you will always get ELPA version to be newer compared to Emacs pretest version. But it is getting complicated... Not sure if it is worth layering the versions that much. >>> (FWIW, I don't understand yet why 29.3 was such an emergency that it was >>> released w/o any warning in advance.) >> >> CVE. > > I haven't seen any CVE number in the announcement. https://security-tracker.debian.org/tracker/CVE-2024-30203 The Emacs release was the announcement, and the first public disclosure of the vulnerability. -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at . Support Org development at , or support my work at