From: John Wiegley <jwiegley@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org, Dmitry Gutov <dgutov@yandex.ru>
Subject: Re: Removing bugs from the blockers
Date: Fri, 13 May 2016 09:33:06 -0700 [thread overview]
Message-ID: <m260uhgbp9.fsf@newartisans.com> (raw)
In-Reply-To: <831t569wwu.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 13 May 2016 11:36:49 +0300")
[-- Attachment #1: Type: text/plain, Size: 936 bytes --]
>>>>> Eli Zaretskii <eliz@gnu.org> writes:
> My conclusion from reviewing these bugs is: I don't really understand how
> come some of the bugs were designated as "blocking".
From my experience working on other projects: there comes a time when people
start noticing that "blocking" bugs get fixed sooner than other bugs, so they
start adding things they "think should be fixed", without asking whether it's
truly a blocking bug.
At Borland we called it "Priority 0"; and guess what happened: nearly every
new bug started getting assigned priority 0, because for a while they were the
only bugs we were paying attention to.
Periodically the blocking list needs recalibration, to return it to its
original purpose. I'd say please unblock every bug you mentioned.
--
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 --]
next prev parent reply other threads:[~2016-05-13 16:33 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
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 [this message]
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=m260uhgbp9.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).