unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: 40990@debbugs.gnu.org
Subject: bug#40990: Improve message-mode and isearch icons
Date: Sat, 02 May 2020 09:23:38 +0300	[thread overview]
Message-ID: <838siavor9.fsf@gnu.org> (raw)
In-Reply-To: <45991686-81b4-a27d-6367-f01bbc20ab10@yandex.ru> (message from Dmitry Gutov on Sat, 2 May 2020 01:12:38 +0300)

> Cc: 40990@debbugs.gnu.org
> From: Dmitry Gutov <dgutov@yandex.ru>
> Date: Sat, 2 May 2020 01:12:38 +0300
> 
> > You do, but I'm asking to help me more.  We should have released 27.1
> > a year ago.
> 
> I really hope that none of my late patches were ever the reason for the 
> delay.

Not you alone.  It's a long series of small changes, each one of them
considered "important".  Together they add up.  And then COVID-19
added its toll.

> And not just my proposals. We're pretty conservative about it. Which is 
> a good thing, of course, but it indicates that we could be moving 
> faster, even if just a bit (be it in allowing more last-minute fixes, or 
> more feature backports, or doing shorter pretests, or starting pretests 
> faster, or all of that together).
> 
> >> Anyway, such discussions should become rare if we somehow manage to
> >> speed up the release cycle someday.
> > Such a someone will be very welcome, indeed.
> 
> Someone?

Someone, somehow, you name it.

> Anyway, for all I know, we could release 27 tomorrow. As soon as we deal 
> with the "modify literal objects" documentation discussion.

There's always "that one last" issue to be fixed.

The only way to speed up our releases that I see is to care less about
stability and regressions.  If you are following the bug list closely,
you will see that we just recently started to get reports about
significant regressions in Emacs 27 (and some in Emacs 26).  Should we
disregard them?  We never did that, not since Emacs 25, at least.





  reply	other threads:[~2020-05-02  6:23 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-30 23:50 bug#40990: Improve message-mode and isearch icons Dmitry Gutov
2020-05-01  6:16 ` Eli Zaretskii
2020-05-01 15:21   ` Dmitry Gutov
2020-05-01 15:43     ` Eli Zaretskii
2020-05-01 15:49       ` Eli Zaretskii
2020-05-01 22:12       ` Dmitry Gutov
2020-05-02  6:23         ` Eli Zaretskii [this message]
2020-05-11  1:42           ` Dmitry Gutov
2020-05-11  2:35             ` Eli Zaretskii
2020-05-11  2:46               ` Dmitry Gutov
2020-05-11  4:17                 ` Eli Zaretskii
2020-05-11 14:18                   ` Dmitry Gutov
2020-05-11 15:53                     ` Eli Zaretskii

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=838siavor9.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=40990@debbugs.gnu.org \
    --cc=dgutov@yandex.ru \
    /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).