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-done@debbugs.gnu.org
Subject: bug#40990: Improve message-mode and isearch icons
Date: Mon, 11 May 2020 05:35:02 +0300	[thread overview]
Message-ID: <835zd3ci7d.fsf@gnu.org> (raw)
In-Reply-To: <3e8277b7-c3dd-56e9-4b40-b817aae264d4@yandex.ru> (message from Dmitry Gutov on Mon, 11 May 2020 04:42:32 +0300)

> Cc: 40990-done@debbugs.gnu.org
> From: Dmitry Gutov <dgutov@yandex.ru>
> Date: Mon, 11 May 2020 04:42:32 +0300
> 
> > 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.
> 
> I don't know what's the best course of action in each case, but if we 
> did make a point of releasing more often (e.g. did time-based releases, 
> for instance), Emacs 27.1 would probably have been less stable. But it 
> would have been released maybe a year ago, and by now we'd already have 
> released, say, 27.2 and 27.3, with more regressions fixed and faster 
> because of exposure to a wider audience, more testing.
> 
> It's a tricky road, but a possible one.

You are just listing the advantages of releasing frequently.  No one
will argue with that, the problem is how to make that happen without
hurting stability.





  reply	other threads:[~2020-05-11  2:35 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
2020-05-11  1:42           ` Dmitry Gutov
2020-05-11  2:35             ` Eli Zaretskii [this message]
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=835zd3ci7d.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=40990-done@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).