From: Eli Zaretskii <eliz@gnu.org>
To: "Kévin Le Gouguec" <kevin.legouguec@gmail.com>
Cc: liwei.ma@gmail.com, emacs-devel@gnu.org
Subject: Re: When will emacs 27.1 be officially released?
Date: Thu, 02 Jul 2020 16:12:24 +0300 [thread overview]
Message-ID: <837dvmxdqf.fsf@gnu.org> (raw)
In-Reply-To: <874kqq2swl.fsf@gmail.com> (message from Kévin Le Gouguec on Thu, 02 Jul 2020 11:00:26 +0200)
> From: Kévin Le Gouguec <kevin.legouguec@gmail.com>
> Cc: liwei.ma@gmail.com, emacs-devel@gnu.org
> Date: Thu, 02 Jul 2020 11:00:26 +0200
>
> > 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 (≈weekly, daily, and continuously
> respectively). Are they more diligent with documentation than Emacs is?
Development snapshots are just that: snapshots of the current
repository's master branch. As such, they are irrelevant to the issue
at hand, because we are talking about releases, not snapshots. (If
someone wants to set up producing daily snapshots for Emacs, I won't
mind, but doing that will not affect the release schedule in any way.)
However, since you asked: at least GDB does require the relevant
documentation changes (NEWS and the manual) with every code change
that has user-visible effect; not sure about the other 2 projects. Of
course, GDB is a very different project in many aspects.
> > 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 "⚠🚨 Red alert! Enriched Text is insecure! 🚨⚠" release
Time flies; sorry for misremembering.
> 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…
What else is new?
next prev parent reply other threads:[~2020-07-02 13:12 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-30 2:52 When will emacs 27.1 be officially released? Liwei Ma
2020-06-30 3:55 ` Eli Zaretskii
2020-06-30 8:12 ` tomas
2020-06-30 9:51 ` Kévin Le Gouguec
2020-06-30 16:58 ` Eli Zaretskii
2020-06-30 18:52 ` Paul Eggert
2020-06-30 19:06 ` Eli Zaretskii
2020-06-30 22:17 ` Paul Eggert
2020-06-30 22:31 ` Dmitry Gutov
2020-07-01 0:03 ` Paul Eggert
2020-07-01 14:29 ` Eli Zaretskii
2020-07-01 17:47 ` Dmitry Gutov
2020-07-01 17:52 ` Paul Eggert
2020-07-01 17:55 ` Dmitry Gutov
2020-07-01 18:13 ` Eli Zaretskii
2020-07-01 18:16 ` Dmitry Gutov
2020-07-01 18:12 ` Eli Zaretskii
2020-07-01 14:33 ` Eli Zaretskii
2020-07-02 3:49 ` Richard Stallman
2020-07-02 13:04 ` Eli Zaretskii
2020-07-03 2:21 ` Richard Stallman
2020-07-02 20:29 ` Tassilo Horn
2020-07-02 20:36 ` Paul Eggert
2020-07-02 20:55 ` Tassilo Horn
2020-07-04 2:53 ` Richard Stallman
2020-07-04 6:41 ` Eli Zaretskii
2020-07-05 2:35 ` Richard Stallman
2020-07-05 14:33 ` Eli Zaretskii
2020-07-03 6:05 ` Eli Zaretskii
2020-07-03 7:24 ` Tassilo Horn
2020-07-03 11:59 ` Eli Zaretskii
2020-07-04 2:52 ` Richard Stallman
2020-06-30 22:09 ` Kévin Le Gouguec
2020-07-01 14:49 ` Eli Zaretskii
2020-07-02 9:00 ` Kévin Le Gouguec
2020-07-02 13:12 ` Eli Zaretskii [this message]
2020-07-02 13:44 ` Kévin Le Gouguec
2020-07-03 0:48 ` Do pretests reach end users? (was: When will emacs 27.1 be officially released?) Dmitry Alexandrov
2020-07-03 6:21 ` Eli Zaretskii
2020-07-03 9:59 ` Do pretests reach end users? Dmitry Gutov
2020-07-03 11:43 ` Eli Zaretskii
2020-07-03 20:23 ` Dmitry Gutov
2020-07-04 6:15 ` Eli Zaretskii
2020-07-04 1:31 ` Dmitry Alexandrov
2020-07-04 6:32 ` Eli Zaretskii
2020-07-05 4:18 ` Dmitry Alexandrov
2020-07-04 11:11 ` Phillip Lord
2020-07-05 4:23 ` Dmitry Alexandrov
2020-07-05 21:15 ` Phillip Lord
2020-07-05 16:55 ` Sean Whitton
2020-06-30 13:01 ` When will emacs 27.1 be officially released? Basil L. Contovounesios
2020-06-30 14:06 ` Stefan Monnier
2020-06-30 14:28 ` Eli Zaretskii
2020-06-30 14:34 ` Rostislav Svoboda
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=837dvmxdqf.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=kevin.legouguec@gmail.com \
--cc=liwei.ma@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).