From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Tentative release schedule for Emacs 29.1 Date: Wed, 16 Nov 2022 15:50:53 +0200 Message-ID: <838rkbgg8y.fsf@gnu.org> References: <87o7v65e0e.fsf@gnus.org> <87edw15l0x.fsf@gnu.org> <87pmflysdt.fsf@gnus.org> <87fsejv7a5.fsf@bzg.fr> <83k03vgi6c.fsf@gnu.org> <87k03vvxs0.fsf@gnu.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="7679"; mail-complaints-to="usenet@ciao.gmane.io" Cc: larsi@gnus.org, emacs-devel@gnu.org, yantar92@gmail.com, kyle@kyleam.com To: Bastien Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Nov 16 14:52:21 2022 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 1ovIpw-0001fT-Cc for ged-emacs-devel@m.gmane-mx.org; Wed, 16 Nov 2022 14:52:20 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ovIom-0002wx-Rt; Wed, 16 Nov 2022 08:51:09 -0500 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 1ovIoc-0002p0-SU for emacs-devel@gnu.org; Wed, 16 Nov 2022 08:51:01 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ovIob-0001Ea-I4; Wed, 16 Nov 2022 08:50:57 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=77SeU/meVF1UMdHErOwKticX1wFtAdPFAwQ7yfwKu2E=; b=gtVYib4cq0RJ +0GOSGhsh/yBopbblzHtDjnR0Tf1534i6YTJRQmKHTL4xFJaskHLiTlGlH+8qMrlV/j37ksfiwO9m DqMhCmYnP6nsyZ1BSlO3/DINYrHldyoqhXmurF6WYDrRbhlWzZVksVudoGaki7X13iABMmJk7suXN b/SGfN78/b0MoCM9S9TPbbIprQYR1T8ugsEBcfb4bW1PS6Bey2A+K+MjQNT04cFwh5UOixwmfiHYk xD7IDNvoaoC34pb+R/YPrHcX8/OoZv502KZa7wl8KWNx9DOM3HgXLIlDXYxiHNJXWcY/ubDqQIS61 WdDnE4qlHrybtWuYMM70xw==; Original-Received: from [87.69.77.57] (helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ovIoZ-0006h8-Te; Wed, 16 Nov 2022 08:50:56 -0500 In-Reply-To: <87k03vvxs0.fsf@gnu.org> (message from Bastien on Wed, 16 Nov 2022 14:23:11 +0100) 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:299927 Archived-At: > From: Bastien > Cc: larsi@gnus.org, emacs-devel@gnu.org, yantar92@gmail.com, kyle@kyleam.com > Date: Wed, 16 Nov 2022 14:23:11 +0100 > > Eli Zaretskii writes: > > > So why are you worried about the Org release, and why are you talking > > about fixing bugs after Emacs 29.1 is released? why not fix them while > > Emacs 29.1 is in pretest? > > My assumption was that we have to release Org 9.6 _before_ the Emacs > 29.1 release cycle begins because the Emacs release branch will be for > bug fixes only and we would not be able to update Org to 9.6 in Emacs > then. I see no reason to require the emacs-29 branch to have a released version of Org in it. From the Emacs POV, what matters is that you don't add new features to Org that is part of the branch after the branching point. Other than that, you can make the official Org 9.6 release whenever you want, as long as what will be on master immediately before the branching point is close enough to 9.6, such that only minor changes (and bugfixes) will be needed there before Emacs 29.1 is released. > Is it so? Or can we release Org 9.6 _after_ Emacs release branch has > been cut and sync it in this release branch after? This is undesirable if what we have now on master is very different from 9.6. If it is not very different, you are free to release Org 9.6 whenever you want.