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: New Package for NonGNU-ELPA: clojure-ts-mode Date: Mon, 28 Aug 2023 14:49:20 +0300 Message-ID: <83o7iridz3.fsf@gnu.org> References: <87il9kksqz.fsf@dfreeman.email> <83350ncbns.fsf@gnu.org> <87cyzrjbd8.fsf@dfreeman.email> <83zg2vav46.fsf@gnu.org> <87o7j99304.fsf@dfreeman.email> <87wmxj27fn.fsf@dfreeman.email> <831qfrptiq.fsf@gnu.org> <57429221-d9be-5791-e975-b3539905e2f6@gutov.dev> <83a5udlj47.fsf@gnu.org> <87a5udk1co.fsf@posteo.net> <835y51kslv.fsf@gnu.org> <7a82c524-1aa1-e755-e377-673ebb107a44@gutov.dev> <83r0nok8s4.fsf@gnu.org> <87il90znco.fsf@yahoo.com> <1977fbef-307b-bcf4-9448-64f26916dd65@gutov.dev> <87edjozlqq.fsf@yahoo.com> <43ddad10-49dd-1c49-ebfe-51689780b315@gutov.dev> <87msyciplu.fsf@posteo.net> <83h6okk3oe.fsf@gnu.org> <87edjoindn.fsf@posteo.net> <83bkesjwuk.fsf@gnu.org> <5b4bfc5b-9fbe-3118-7475-66fe19fa9d92@gutov.dev> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="27687"; mail-complaints-to="usenet@ciao.gmane.io" Cc: philipk@posteo.net, luangruo@yahoo.com, danny@dfreeman.email, stefankangas@gmail.com, emacs-devel@gnu.org, manuel.uberti@inventati.org To: Dmitry Gutov Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Mon Aug 28 13:50:54 2023 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 1qaali-00074X-4u for ged-emacs-devel@m.gmane-mx.org; Mon, 28 Aug 2023 13:50:54 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qaal2-0003pK-LA; Mon, 28 Aug 2023 07:50:12 -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 1qaako-0003kB-7R for emacs-devel@gnu.org; Mon, 28 Aug 2023 07:50:00 -0400 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 1qaakk-0007Bv-Ja; Mon, 28 Aug 2023 07:49:55 -0400 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=4q06gojZdonSn+6gxm2BT6aYWj8n0fFAmEgCAmWHkyg=; b=p5uZqMbBQ5R2 D4cYHEDBW2TWKH6B14ooXQxT+Y1J2qN+DIXlbm+N7/GqBchExBlXDcG/ndB6/M0sAq1RlNQq0Rnti GG8HDeX6++icIxFiy1Pt2J683TjVAkxFzekD/cOn5ZaIptdQ3phNBnMUScnxzbf0AlJjX47qOeR9n /zbS9HYKWpzObCJDc/P1poW6m5cYqjKjVntNt16N1h1i4NPXt85yxAR/x2fC0Cs/Ik2+j1uRDgykd KIGmgY4NnnpYiYqIX9fF0o3WW4JjNo9o5aOrjd7ZMCR9Pc10YB4Wa6pDbv+jRQdaj4eOBonm5Pm0P jFbGBo+oh3AOdoLA6RkjNA==; In-Reply-To: <5b4bfc5b-9fbe-3118-7475-66fe19fa9d92@gutov.dev> (message from Dmitry Gutov on Mon, 28 Aug 2023 00:22:43 +0300) 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:309427 Archived-At: > Date: Mon, 28 Aug 2023 00:22:43 +0300 > Cc: luangruo@yahoo.com, danny@dfreeman.email, stefankangas@gmail.com, > emacs-devel@gnu.org, manuel.uberti@inventati.org > From: Dmitry Gutov > > On 27/08/2023 19:04, Eli Zaretskii wrote: > > >> How did you decide when to draw the line between Emacs 29 and Emacs 30? > > > > That's when the release branch is cut. But doing so doesn't determine > > the future release date, except very roughly. > > > > When to cut the release branch is up to the maintainers, and IME the > > reasons are not fixed. The mount of new features and the time since > > the last major release are important factors, though. > > There is a fair amount of leeway and personal judgment in when to > consider a release to be "ready", so it's possible that we could try. We could try what? > > There's also a problem that we rarely can promise a certain release > > date, because there are factors out of our control, such as the bugs > > and regressions reported during pretest, the resources that can > > dwindle due to "Real Life", etc. > > If we do manage to release Emacs versions (most or all) before Debian's > cutoff dates, that would mean larger user base and more testing to be > done on the release right away. Perhaps if we fall into cadence, some > people would then come regularly from Debian's side and test the > pretests in advance, to check that everything is in order. > > That's a possible "two way street", but it's not something that can be > agreed to beforehand, I guess, not in the least because we won't want to > give any guarantees at the start. I don't think anyone will argue with the advantages. The problems are much more practical. We are all volunteers here, so promises of a release date are notoriously unreliable. I intended to have the first pretest of Emacs 29 in February, but only succeeded to get it out in April, for reasons that were completely out of my control.