From: Evan Prodromou <evan@glug.org>
Subject: Re: Handling BUGS.
Date: Fri, 22 Mar 2002 13:40:01 -0600 [thread overview]
Message-ID: <87elic8k8e.fsf@tyrell.bad-people-of-the-future.san-francisco.ca.us> (raw)
In-Reply-To: <E16oUTN-0002s4-00@giblet> (Thien-Thi Nguyen's message of "Fri, 22 Mar 2002 11:13:09 -0800")
>>>>> "TN" == Thien-Thi Nguyen <ttn@giblet.glug.org> writes:
Me> In other words, concentrate on the release, not the
Me> bug-tracking "tool". What you're suggesting gives everyone an
Me> excuse to ignore the BUGS file and (totally insufficient)
Me> system in place until the "next" system appears.
TN> so i would have to disagree w/ your point, but obliquely; it
TN> is precisely the act of concentrating on release that is the
TN> motivating factor here, and it seems the proposed changes are
TN> well thought-out, or in the process of becoming so.
Well, then, if that's the case, I'd say go for it.
HOWEVER, it seems that perhaps maintaining the current bug file format
(except, of course, splitting up bugs between files) might get one
"there" faster than hoping for -- or hacking on -- an RFC822 parser.
TN> when you say "it is more important to do this than that" you
TN> lose sight of the fact that parallel effort is possible and
TN> indeed encouraged -- good project manglement is not so much
TN> about constraining (controlling, contorting) efforts into a
TN> single thread, but more about defining a future sync point
TN> where the multiple threads can come together (in a harmonious
TN> way hopefully).
This is true. However, good _release_ management has everything to do
with prioritizing energy and focus, and having dependable
processes.
~ESP
--
Evan Prodromou
evan@glug.org
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2002-03-22 19: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
2002-03-22 19:13 ` Thien-Thi Nguyen
2002-03-22 19:40 ` Evan Prodromou [this message]
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=87elic8k8e.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).