From: Evan Prodromou <evan@glug.org>
Subject: Re: Handling BUGS.
Date: Fri, 22 Mar 2002 11:40:26 -0600 [thread overview]
Message-ID: <87lmcko60l.fsf@tyrell.bad-people-of-the-future.san-francisco.ca.us> (raw)
In-Reply-To: <87g02t4zgn.fsf@raven.i.defaultvalue.org> (Rob Browning's message of "Thu, 21 Mar 2002 11:12:24 -0600")
[-- Attachment #1: Type: text/plain, Size: 981 bytes --]
>>>>> "RB" == Rob Browning <rlb@defaultvalue.org> writes:
RB> What about a semi-trivial upgrade to our bug handling
RB> infrastructure?
Not my place to say, but: the system you're suggesting isn't going to
be The Right Thing, nor will it be particularly easier to work with or
more complete with than what you have now.
I would say that any time or effort devoted to hacking on a quasi
bug-tracking system would be better spent putting bugs in the current
system, tracking them, and fixing them for 1.6 release.
After that release, start using savannah's Sourceforge bug-tracker, or
build one that's all the way "right" with Guile.
In other words, concentrate on the release, not the bug-tracking
"tool". What you're suggesting gives everyone an excuse to ignore the
BUGS file and (totally insufficient) system in place until the "next"
system appears.
OK, that's my advice. Take it however you want.
~ESP
--
Evan Prodromou
evan@glug.org
[-- Attachment #2: Type: application/pgp-signature, Size: 184 bytes --]
next prev parent reply other threads:[~2002-03-22 17:40 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-21 17:12 Handling BUGS Rob Browning
2002-03-21 23:09 ` Neil Jerram
2002-03-22 0:54 ` Rob Browning
2002-03-22 9:03 ` Neil Jerram
2002-03-22 6:35 ` Thien-Thi Nguyen
2002-03-22 9:14 ` Neil Jerram
2002-03-22 14:25 ` Rob Browning
2002-03-22 19:32 ` Thien-Thi Nguyen
2002-03-22 17:40 ` Evan Prodromou [this message]
2002-03-22 19:13 ` Thien-Thi Nguyen
2002-03-22 19:40 ` Evan Prodromou
2002-03-22 20:08 ` Thien-Thi Nguyen
2002-03-22 20:34 ` Evan Prodromou
2002-03-22 21:41 ` Thien-Thi Nguyen
2002-03-22 22:33 ` Rob Browning
2002-03-23 0:53 ` Thien-Thi Nguyen
2002-03-23 12:14 ` Marius Vollmer
2002-03-23 14:12 ` Rob Browning
2002-03-23 14:59 ` Rob Browning
2002-03-24 19:14 ` Marius Vollmer
2002-03-23 21:43 ` Thien-Thi Nguyen
2002-03-24 13:37 ` Marius Vollmer
2002-03-24 19:31 ` Thien-Thi Nguyen
2002-03-24 20:40 ` Marius Vollmer
2002-03-24 21:13 ` Rob Browning
2002-03-24 22:00 ` Marius Vollmer
2002-03-25 3:57 ` Rob Browning
2002-03-25 8:32 ` Thien-Thi Nguyen
2002-03-25 21:05 ` Marius Vollmer
2002-03-25 21:34 ` Thien-Thi Nguyen
2002-03-25 22:31 ` Marius Vollmer
2002-03-25 23:22 ` Thien-Thi Nguyen
2002-03-25 23:39 ` Thien-Thi Nguyen
2002-03-22 20:34 ` Thien-Thi Nguyen
2002-03-22 22:31 ` 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=87lmcko60l.fsf@tyrell.bad-people-of-the-future.san-francisco.ca.us \
--to=evan@glug.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).