From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: =?utf-8?Q?K=C3=A9vin_Le_Gouguec?= Newsgroups: gmane.emacs.devel Subject: Re: When will emacs 27.1 be officially released? Date: Thu, 02 Jul 2020 11:00:26 +0200 Message-ID: <874kqq2swl.fsf@gmail.com> References: <28BB39D5-074F-4450-A747-C2BFB37AA482@gnu.org> <87pn9g6fuo.fsf@gmail.com> <83bll0ze1x.fsf@gnu.org> <87a70kw6hx.fsf@gmail.com> <83tuyrxpcj.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="13673"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) Cc: liwei.ma@gmail.com, emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Thu Jul 02 11:01:37 2020 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 1jqv68-0003R8-LN for ged-emacs-devel@m.gmane-mx.org; Thu, 02 Jul 2020 11:01:36 +0200 Original-Received: from localhost ([::1]:39756 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jqv67-0002LX-Jo for ged-emacs-devel@m.gmane-mx.org; Thu, 02 Jul 2020 05:01:35 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:45016) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jqv56-0001HL-46 for emacs-devel@gnu.org; Thu, 02 Jul 2020 05:00:32 -0400 Original-Received: from mail-wm1-x344.google.com ([2a00:1450:4864:20::344]:35903) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1jqv54-0006La-BV; Thu, 02 Jul 2020 05:00:31 -0400 Original-Received: by mail-wm1-x344.google.com with SMTP id 17so26957579wmo.1; Thu, 02 Jul 2020 02:00:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:subject:references:date:in-reply-to:message-id :user-agent:mime-version:content-transfer-encoding; bh=xM5EPx9fNdrlHc8nWh2OuqepyPzn8EOZdNPta61Ae6U=; b=FchhTDQOjG5yVJSHbEOWObgnzJvmKjxuD8jDGQBB3w4DMxG+MEZvfDYWttzb7SfsvT jf9r6P+jISuqrl3ktOJJCcnFIEWi76GWUFfylScjG78NhkXRNAr9vJUtsFLnXRglhPy0 ecof3tXGTrvSq2qDqN2WK6Lpy8kCz/XlRmjhiB61ys9AcjlshUUxXdY0RCTsKPAOdoZy xW/Cz3R1PXYtPndb3tNA44HVRUW7N7/UnCY7yR5QElX0epPgBM5W9J+bYNBRybXCUQuN cA1BOa1XtQqlB3Bw5wDP+cVd/w57Wr3Aan4e0zEkfSZT6SGVVU7Kf8yx7AKiQ4xFFDEi eA1g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:references:date:in-reply-to :message-id:user-agent:mime-version:content-transfer-encoding; bh=xM5EPx9fNdrlHc8nWh2OuqepyPzn8EOZdNPta61Ae6U=; b=FN8R47VaOkMHCGJaXYxSFgfrSK9fFXL8muxtkn1Xv4D7eBHF+YY3OOip437IqIqhTE ZUCoPiONSMkKliXLmbDvXSlKZDG/0jgDXcNj3tgGumbPPYihuAW9QZsYFxBJqeF1Unz+ a0aTXEnzMAlKKMYTovgeFtGqB0QomGhpdy1OQ4VVY2D95ZLw1DSdVCvmqr7ZedQIAWmN KCdrM2IMftELECY+XTU/8/O8nC4fT7XDUfbRgUEbM3n6YxFLm44Ews1K0FaGWuBLgrjc epxaGzeHT0jBu3oEbHL+3HXI3f51Z2iRJuBTXUWTPla6kAtGR3elX5m+F037m0LibKDt M3aA== X-Gm-Message-State: AOAM532mqC9dWfLZT0Wit++UkCZxaV5ckTtvWQLD+2rKqctu3YIaYsWB CJNStjvFekG3lXBBlPvAniZdReY/Zyo= X-Google-Smtp-Source: ABdhPJyMKjdpVOUzzgX0eJ0bX/NnLFFcysJym0VQ7X62yK8F5zEN/J8h6C5mMg4If7DwLoU/jhiAkQ== X-Received: by 2002:a05:600c:2182:: with SMTP id e2mr30141496wme.186.1593680427708; Thu, 02 Jul 2020 02:00:27 -0700 (PDT) Original-Received: from my-little-tumbleweed (200.143.13.109.rev.sfr.net. [109.13.143.200]) by smtp.gmail.com with ESMTPSA id 51sm5416893wrc.44.2020.07.02.02.00.26 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 02 Jul 2020 02:00:27 -0700 (PDT) In-Reply-To: <83tuyrxpcj.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 01 Jul 2020 17:49:16 +0300") Received-SPF: pass client-ip=2a00:1450:4864:20::344; envelope-from=kevin.legouguec@gmail.com; helo=mail-wm1-x344.google.com X-detected-operating-system: by eggs.gnu.org: No matching host in p0f cache. That's all we know. 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, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=_AUTOLEARN X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 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" Xref: news.gmane.io gmane.emacs.devel:252621 Archived-At: Eli Zaretskii writes: >> I admit I don't see an easy way out of this situation. I suspect some >> users (the kind who use Debian Sid, Ubuntu PPAs, or any rolling release >> distro) would flock to "nightly" tarballs and would not get overly >> fussed about incomplete documentation, but that's just a guess. > > A decision to disregard our documentation is not mine to take > (although I personally do have an opinion, of course). It is > something the community as a whole needs to decide, and then we will > have to convince the Powers that Be of the GNU project; good luck with > that! Mmm. I see that e.g. GCC[1], GDB[2] and Guix[3][4] put out "development snapshots" fresh off the master branch (=E2=89=88weekly, daily, and continu= ously respectively). Are they more diligent with documentation than Emacs is? [1] https://gcc.gnu.org/snapshots.html [2] https://www.gnu.org/software/gdb/current/ [3] https://guix.gnu.org/download/latest/ [4] (Also, that's neither here nor there, but kudos to Guix for automating the whole thing; AFAICT from the download URL, thanks to their CI system, it takes zero effort for them to (1) build the latest commit (2) test the result (3) archive it (4) make it available on their website.) >> > Especially since an >> > emergency bugfix release is also not something we can do quickly >> > enough, as one or two occurrences in the past have shown. >>=20 >> I dimly remember that 25.3 sparked some debate regarding the difficulty >> of putting out "targeted bugfix" releases as quickly as we'd like. I >> don't remember the conclusions; is there anything specific to Emacs that >> prevents us from getting better? > > I think it was 26.3, and the problem is not the decision, the problem > was how much time it took. Too much, IMO. 25.3 was the "=E2=9A=A0=F0=9F=9A=A8 Red alert! Enriched Text is insecure! = =F0=9F=9A=A8=E2=9A=A0" release; I don't see anything in the 26.3 NEWS that suggests "an emergency bugfix release", though it's entirely possible that this one also took too much time. Here are some (lengthy) threads that the 25.3 release process triggered. Off the top of my head, I don't remember if there were any conclusions wrt hastening this process=E2=80=A6 https://lists.gnu.org/archive/html/emacs-devel/2017-09/msg00401.html https://lists.gnu.org/archive/html/emacs-devel/2017-09/msg00211.html