From: Chong Yidong <cyd@MIT.EDU>
To: joakim@verona.se
Cc: emacs-devel@gnu.org
Subject: Re: Milestones for bugs in the tracker?
Date: Sun, 10 Aug 2008 14:23:48 -0400 [thread overview]
Message-ID: <20080810142348.40zcbzpxgc0sc04g@webmail.mit.edu> (raw)
In-Reply-To: <m37iapns27.fsf@verona.se>
> - Which bugs are critical for the release? I know about etc/FOR-RELEASE,
> but should we really spread out information in several places?
Thanks for helping look through the bug list.
At this stage, we should try to fix every bug in the bug tracker.
Later, as we
get closer to the release, we might want to set priorities (e.g.
distinguishing
regressions from long-standing bugs). But right now, please treat
every bug as
one that should be fixed.
prev parent reply other threads:[~2008-08-10 18:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-10 9:21 Milestones for bugs in the tracker? joakim
2008-08-10 18:23 ` Chong Yidong [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=20080810142348.40zcbzpxgc0sc04g@webmail.mit.edu \
--to=cyd@mit.edu \
--cc=emacs-devel@gnu.org \
--cc=joakim@verona.se \
/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).