unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Evan Prodromou <evan@glug.org>
Cc: guile-devel@gnu.org
Subject: Re: Bug Reports for 1.6 Release Candidates
Date: Sun, 17 Mar 2002 21:59:48 -0600	[thread overview]
Message-ID: <87vgbuedaj.fsf@tyrell.bad-people-of-the-future.san-francisco.ca.us> (raw)
In-Reply-To: <87y9gq8rm6.fsf@raven.i.defaultvalue.org> (Rob Browning's message of "Sun, 17 Mar 2002 21:46:57 -0600")

>>>>> "RB" == Rob Browning <rlb@defaultvalue.org> writes:

    RB> Though bug tracking seems to me like *exactly* the kind of
    RB> thing for which you want a relational DB.

Absolutely, absolutely. That said, I think if we (actually, it's not
*me* making the decisions, so I dunno what I'm talking about with this
we stuff, and we have yet to hear from Marius on the issue) get hung
up on having Only The Best Tracking System, we'll lose sight of the
fact that we're trying to get out a release, get it out with minimum
embarassing buggage, and get it out sooner rather than later.

I'd recommend keeping the BUGS file for now, and maybe switching over
to a more civilized bug-tracker after the 1.6 release.

~ESP

-- 
Evan Prodromou
evan@glug.org

_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel


  reply	other threads:[~2002-03-18  3:59 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 [this message]
2002-03-18 14:17           ` Rob Browning
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=87vgbuedaj.fsf@tyrell.bad-people-of-the-future.san-francisco.ca.us \
    --to=evan@glug.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).