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 18:53:33 +0300	[thread overview]
Message-ID: <83h7wmbh8i.fsf@gnu.org> (raw)
In-Reply-To: <60322abc-7b56-db02-3a41-2bfc9ea59b9c@yandex.ru> (message from Dmitry Gutov on Mon, 11 May 2020 17:18:15 +0300)

> Cc: 40990-done@debbugs.gnu.org
> From: Dmitry Gutov <dgutov@yandex.ru>
> Date: Mon, 11 May 2020 17:18:15 +0300
> 
> For example, if we target, say, a new Emacs release every 6 months, then 
> it will be 2 months development, 2 months stabilization, and 2 months 
> prerelease (with new developments doing to the master for the last 4 
> months).

2 months for development is way too little.

> With cycles like that, there will also be less temptation to "sneak that 
> last feature in", or land an experimental feature later in the cycle. 
> Developers will also moderate the risk themselves.

I will believe that when I see it ;-)

Anyway, serious discussion of this should be on emacs-devel.





      reply	other threads:[~2020-05-11 15:53 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
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 [this message]

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=83h7wmbh8i.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).