From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Danny Freeman Newsgroups: gmane.emacs.devel Subject: Re: Brand new clojure support in Emacs ;-) Date: Tue, 05 Sep 2023 22:42:05 -0400 Message-ID: <87sf7sc942.fsf@dfreeman.email> References: <87il9kksqz.fsf@dfreeman.email> <83350ncbns.fsf@gnu.org> <87cyzrjbd8.fsf@dfreeman.email> <83zg2vav46.fsf@gnu.org> <87o7j99304.fsf@dfreeman.email> <87zg2hsyrd.fsf@dfreeman.email> <87h6ontwfv.fsf@posteo.net> <835y4ucrz3.fsf@gnu.org> <831qficgin.fsf@gnu.org> <87ttsehwab.fsf@dfreeman.email> <87fs3x6ge7.fsf@gmail.com> <87v8cthmzl.fsf@dfreeman.email> <87a5u56atj.fsf@gmail.com> <87r0nhhgb5.fsf@dfreeman.email> <834jkdaz6d.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="19373"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Stefan Kangas , emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Sep 06 04:47:11 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 1qdiZS-0004nw-S0 for ged-emacs-devel@m.gmane-mx.org; Wed, 06 Sep 2023 04:47:11 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qdiYa-0007mf-QA; Tue, 05 Sep 2023 22:46:16 -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 1qdiYY-0007mS-II for emacs-devel@gnu.org; Tue, 05 Sep 2023 22:46:14 -0400 Original-Received: from out-224.mta1.migadu.com ([2001:41d0:203:375::e0]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qdiYU-0001pF-7Y for emacs-devel@gnu.org; Tue, 05 Sep 2023 22:46:14 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dfreeman.email; s=key1; t=1693968354; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=o1l71kfQFVHD12mDKFJCwIP3Yg9ytNcw/dLd2Dgs+C0=; b=LTG5rG3HYM7TFv2KReRViGILCNUtGuCIcbYoCjTGuifg+73Z5HOFqMzyp/52Ug/tG92VA9 I32JKYhn5WYN30uH7lXm/vhL4PSfZrc+Var3qv0e/4v3EISBmJoneY6alg+Y0cuI2z4z7X sdQmRag+N7l7v/Uw3bdtFOtXYn53rms= X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. In-reply-to: <834jkdaz6d.fsf@gnu.org> X-Migadu-Flow: FLOW_OUT Received-SPF: pass client-ip=2001:41d0:203:375::e0; envelope-from=danny@dfreeman.email; helo=out-224.mta1.migadu.com X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 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, 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:310168 Archived-At: Eli Zaretskii writes: >> Thanks again for being willing to revisit this decision. Emacs 30 is >> still at least a year away, so I think late spring or early summer >> 2024 could be a good time to do it. > > If this will be a package that's not bundled with Emacs, its > development and release schedule doesn't have to be synchronized with > Emacs, unless the package needs some features not currently available > in Emacs 29 or earlier. But if there's intent to perhaps include this > package with Emacs, then for that to happen in Emacs 30.1, the > decision should be earlier, perhaps within the next 4-5 months. > Because, though the _release_ of Emacs 30 is probably a year or so > away, we might decide to cut the emacs-30 release branch before the > end of 2023, and any additional new features after that would be > harder to get into the release branch. Just wanted to respond here to let you know I didn't let this message get lost in the sea of emails over the last week. I will be sure to keep this time frame in mind during the decision making process. All the best, -- Danny Freeman