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: Thu, 04 Apr 2024 17:46:26 +0000 Message-ID: <87il0xt40d.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> <86o7b0iy5i.fsf@gnu.org> <87edbwdqpv.fsf@gmx.de> <86frwbj171.fsf@gnu.org> <87zfujdazh.fsf@gmx.de> <868r23iq29.fsf@gnu.org> <87o7az7f2o.fsf@gmx.de> <87r0fmk5zs.fsf@gmx.de> <86ttki8v92.fsf@gnu.org> <87jzle4hrd.fsf@gmx.de> <86plv571rg.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="18274"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Michael Albinus , emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Thu Apr 04 19:47:06 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 1rsRB3-0004Rb-U2 for ged-emacs-devel@m.gmane-mx.org; Thu, 04 Apr 2024 19:47:06 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1rsRAM-00058A-W7; Thu, 04 Apr 2024 13:46:23 -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 1rsRAM-000582-0N for emacs-devel@gnu.org; Thu, 04 Apr 2024 13:46:22 -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 1rsRAI-0003dA-CT for emacs-devel@gnu.org; Thu, 04 Apr 2024 13:46:21 -0400 Original-Received: from submission (posteo.de [185.67.36.169]) by mout01.posteo.de (Postfix) with ESMTPS id 44BBD240027 for ; Thu, 4 Apr 2024 19:46:15 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1712252775; bh=lkWb9CoOjwgcAJDUCYkweNLjzh1fBdc7TGRYMV2ey+Q=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version:Content-Type: From; b=XthKFNrddPe+x2dJ8MEUsa5Z3OA2mrOeT48av3R8zs/7kZ8mD0d9fsMFnx8OaZAfG IJh6uINskxapFxZ774zUryYCku5m9n+YdgDnkVz9nUd3f7wZPJhmkhQgiP9GBvHaaM 1cHuEk730rIUKpJt8KkGCLCSwwXKd0Vzmp2EJd3RRy1wMSeEYcaHtRUfErkT28n3Kp kbInsZWBTCmbdnsaiLx/nCp9QjFfFcK64l5AR4+cyeKcw8utqNZkJ1O/0CDiJacV7/ zFccVQ2kiHWhzTuITHYB5XZyIO5BPuWUjmRRLVK9/Lp6+fxut4A4DcAGaGrgnMfPGR G/+mSkmhHOteA== Original-Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4V9TYy4Zdgz9rxG; Thu, 4 Apr 2024 19:46:14 +0200 (CEST) In-Reply-To: <86plv571rg.fsf@gnu.org> 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=unavailable 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:317525 Archived-At: Eli Zaretskii writes: >> Perhaps we need also to mention Org, but this I don't now for sure. > > Ihor will tell, but I believe the Org version on the release branch is > already kept in a ready state. Yup. On Emacs (bugfix) release branch, we are careful to sync only the latest stable (bugfix) Org version that does not contain any risky changes. Occasionally, we may have risky changes if they are themselves critical (like fixing complete breakage). So, having a notification that new Emacs release is imminent might still be of use, so that we can sync the critical changes in the rare situations when there is both urgent Emacs release, urgent Org mode release, and the urgent Org mode release is not yet in sync (e.g. if Kyle is busy with something and delayed sync). -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at . Support Org development at , or support my work at