unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: John Wiegley <jwiegley@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: dgutov@yandex.ru, emacs-devel@gnu.org
Subject: Re: [Emacs-diffs] emacs-25 d0d9f55: Allow newlines inside cl function arglists
Date: Fri, 13 May 2016 09:26:06 -0700	[thread overview]
Message-ID: <m2eg95gc0x.fsf@newartisans.com> (raw)
In-Reply-To: <83ziru8htv.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 13 May 2016 11:47:56 +0300")

[-- Attachment #1: Type: text/plain, Size: 1461 bytes --]

>>>>> Eli Zaretskii <eliz@gnu.org> writes:

>> 3. The presence of the bug makes basic functionality annoying or cumbersome.
>> 
>> 4. The presence of the bug would cause widespread breakage in community
>> packages, unless there is an acceptable upgrade path.

> Thanks. However, items 3 and 4 are IMO too vague, and can fit almost any
> issue, as the criteria are open to subjective interpretation.

Yes, if a person lobbies for a bug to be included in the blocking list under
these criteria, they'd need to do some convincing on these points.

> Also, we used to have criteria related to the age of the bug, on the
> assumption that old bugs are less likely to be critical. I'm not saying that
> we must keep such a criterion, but I think it should at least be considered
> for inclusion.

Sure, I'd be willing to add this.  A bug that's been in the past 5 versions of
Emacs can likely be in a 6th.

>> In other words, as long as the presence of bug X doesn't make Emacs
>> unsuitable for use, I'm willing to live with bug X until the next point
>> release.

> This sounds like much more stringent criterion than the others.

I meant it to summarize what a bug should "feel" like to be considered
blocking, but I didn't add it to the list. "Unsuitable" is even vaguer still.

-- 
John Wiegley                  GPG fingerprint = 4710 CF98 AF9B 327B B80F
http://newartisans.com                          60E1 46C4 BD1A 7AC1 4BA2

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 629 bytes --]

  reply	other threads:[~2016-05-13 16:26 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20160509235343.17047.73943@vcs.savannah.gnu.org>
     [not found] ` <20160509235343.759D0220128@vcs.savannah.gnu.org>
2016-05-10  1:34   ` [Emacs-diffs] emacs-25 d0d9f55: Allow newlines inside cl function arglists Stefan Monnier
2016-05-10 10:11     ` Dmitry Gutov
2016-05-10 10:21       ` Andreas Schwab
2016-05-10 10:31         ` Dmitry Gutov
2016-05-10 11:27           ` Andreas Schwab
2016-05-10 11:33             ` Dmitry Gutov
2016-05-10 11:57               ` Andreas Schwab
2016-05-10 12:01                 ` Dmitry Gutov
2016-05-10 12:36                   ` Andreas Schwab
2016-05-10 12:49                     ` Dmitry Gutov
2016-05-10 21:14                       ` Stefan Monnier
2016-05-10 21:26                         ` Dmitry Gutov
2016-05-11  0:39                           ` Dmitry Gutov
2016-05-11 22:40                             ` Dmitry Gutov
2016-05-11  1:47   ` John Wiegley
2016-05-12 19:23     ` Eli Zaretskii
2016-05-12 21:23       ` John Wiegley
2016-05-13  8:47         ` Eli Zaretskii
2016-05-13 16:26           ` John Wiegley [this message]
2016-05-12 21:35     ` Removing bugs from the blockers Dmitry Gutov
2016-05-13  8:36       ` Eli Zaretskii
2016-05-13 10:30         ` Lars Ingebrigtsen
2016-05-13 14:12           ` Eli Zaretskii
2016-05-13 16:28             ` John Wiegley
2016-05-13 20:20             ` Lars Ingebrigtsen
2016-05-16 17:51               ` Eli Zaretskii
2016-05-13 12:48         ` Dmitry Gutov
2016-05-13 16:33         ` John Wiegley
2016-06-09 13:04         ` Nix
2016-06-09 21:09           ` bug#21182 (was Removing bugs from the blockers) Mike Kupfer
2016-06-10 11:33             ` Nix
2016-05-13 11:30       ` Removing bugs from the blockers Kaushal Modi
2016-05-13 11:38         ` Dmitry Gutov

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=m2eg95gc0x.fsf@newartisans.com \
    --to=jwiegley@gmail.com \
    --cc=dgutov@yandex.ru \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    /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).