From: Rob Browning <rlb@defaultvalue.org>
Cc: guile-devel@gnu.org
Subject: Re: Bug Reports for 1.6 Release Candidates
Date: Mon, 18 Mar 2002 08:17:54 -0600 [thread overview]
Message-ID: <87lmcq7yel.fsf@raven.i.defaultvalue.org> (raw)
In-Reply-To: <87vgbuedaj.fsf@tyrell.bad-people-of-the-future.san-francisco.ca.us> (Evan Prodromou's message of "Sun, 17 Mar 2002 21:59:48 -0600")
Evan Prodromou <evan@glug.org> writes:
> I'd recommend keeping the BUGS file for now, and maybe switching
> over to a more civilized bug-tracker after the 1.6 release.
ABSOLUTELY.
Just wanted to make sure no one thought I was talking about short-term
changes here :> For 1.6, the BUGS and TODO files will do quite nicely.
I was just musing about things we might want to do later, and I don't
know that we'd ever do some of the fancier stuff.
I do think that we should probably use the TODO file to list the BUGS
that are release critical in the per-release section(s). Ideally
looking at the TODO should give you a complete overview of what has to
be done.
--
Rob Browning
rlb @defaultvalue.org, @linuxdevel.com, and @debian.org
Previously @cs.utexas.edu
GPG=1C58 8B2C FB5E 3F64 EA5C 64AE 78FE E5FE F0CB A0AD
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2002-03-18 14:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-16 18:50 Bug Reports for 1.6 Release Candidates Evan Prodromou
2002-03-17 3:05 ` Evan Prodromou
2002-03-17 8:22 ` Thien-Thi Nguyen
2002-03-17 16:46 ` Evan Prodromou
2002-03-18 3:46 ` Rob Browning
2002-03-18 3:59 ` Evan Prodromou
2002-03-18 14:17 ` Rob Browning [this message]
2002-04-03 3:39 ` Thien-Thi Nguyen
2002-04-03 4:18 ` Rob Browning
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/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87lmcq7yel.fsf@raven.i.defaultvalue.org \
--to=rlb@defaultvalue.org \
--cc=guile-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.
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).