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:09:15 +0200 Message-ID: <83k03vgi6c.fsf@gnu.org> References: <87o7v65e0e.fsf@gnus.org> <87edw15l0x.fsf@gnu.org> <87pmflysdt.fsf@gnus.org> <87fsejv7a5.fsf@bzg.fr> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="13359"; 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:10:00 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 1ovIAx-0003EI-Cg for ged-emacs-devel@m.gmane-mx.org; Wed, 16 Nov 2022 14:09:59 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ovIAM-0005Zn-S9; Wed, 16 Nov 2022 08:09:22 -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 1ovIAL-0005ZL-4Z for emacs-devel@gnu.org; Wed, 16 Nov 2022 08:09:21 -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 1ovIAK-000567-Mb; Wed, 16 Nov 2022 08:09:20 -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=Y9lwY6KIO8AB8Mm87DyXKuAcf5NCqsTwtsCz+O2atR8=; b=CHV3iuc1Hi6z 4zgmIT6V3ELf1O0dx78jVR8Pt0cEogEySXXYCvrewdcKO1o2x8GbeT3aQIwGi4NtAmvBWFz9zEO4+ LLOrlGv3qpiDcuCjQpqa2kd3UbGp+rvgifi/cXWj3bxKlgRjv0a1kiilgpNS+bfBzGT7om6LZVh1T NFj78LzfX9rSj3apk8x4vUejI24ogVEIQdrAj3/L8uacNPXWeD78n67bOlzAFbnE00ULpP9+XN1TI a92G04mOy/9xD7rP0GWSbRSDjCeb0t2KeeXl3aLdGPkZRwb2j8LGvfuvBBvawfsmRFOncIZ6dmw5q eEM48IRtcgVbWf2/YiT32w==; 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 1ovIAH-00068M-CU; Wed, 16 Nov 2022 08:09:17 -0500 In-Reply-To: <87fsejv7a5.fsf@bzg.fr> (message from Bastien on Wed, 16 Nov 2022 05:43:14 +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:299918 Archived-At: > From: Bastien > Cc: emacs-devel@gnu.org, Ihor Radchenko , Kyle Meyer > > Date: Wed, 16 Nov 2022 05:43:14 +0100 > > Lars Ingebrigtsen writes: > > > We're aiming to cut the new release branch in late November. > > Is it still the plan? Yes. > Ideally, a 2-3 weeks delay between Emacs 29.1 and Org 9.6 would help > us fix new bugs and release 9.6.1 to be included in Emacs 29.1. Sorry, I don't follow. The schedule above is for cutting the release branch, which will start the Emacs 29.1 release cycle and will be followed by a period of pretest. When that preset ends and Emacs 29.1 will be released is not yet known beyond some general hopes. 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? > Given that delay and given Emacs release expectations, what would be > the best time to release Org? > > If we can release 9.6 in late november and fix bugs until mid-december > then release and sync 9.6.1, that'd be great. Late November is just when we cut the emacs-29 release branch, so I don't see how the release of Org 9.6 could be related to that in any way. What am I missing?