From: Rob Browning <rlb@defaultvalue.org>
Subject: Handling BUGS.
Date: Thu, 21 Mar 2002 11:12:24 -0600 [thread overview]
Message-ID: <87g02t4zgn.fsf@raven.i.defaultvalue.org> (raw)
What about a semi-trivial upgrade to our bug handling infrastructure?
(1) create a top level guile CVS module called guile-bugs.
(2) create a shallow directory tree:
guile-bugs/active/
guile-bugs/resolved/
(3) create a new file in active/ per bug containing the current
contents of it's entry in 1.5/BUGS or 1.7/BUGS -- merge any
duplicates. (a simple 'ls | sort -n | tail -1" can tell us what
the next bug number should be)
(4) Add an "affects" field to every bug, and whenever a bug's
"affects" field becomes empty, move it to resolved/. The
affects field would be something like: "affects: 1.4 1.5 1.7" or
perhaps (affects "1.4" "1.5" "1.7") -- not sure if scheme-forms
would buy us anything we care about...
(5) modify the RELEASE process to require that a current BUGS file
be generated from guile-bugs and added to the release CVS tree
at release time (just before tagging the release). This file
would be (auto)generated from guile-bugs/active based on the
contents of the "affects" fields.
(6) add a note to the top of the auto-generated BUGS files
indicating that they're auto-generated and pointing people at
the guile-bugs CVS module and/or any web pages we might
auto-generate from guile-bugs.
This seems like it would be a lot more flexible than what we have now,
and shouldn't be much work.
Thoughts?
--
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 reply other threads:[~2002-03-21 17:12 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-21 17:12 Rob Browning [this message]
2002-03-21 23:09 ` Handling BUGS 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
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=87g02t4zgn.fsf@raven.i.defaultvalue.org \
--to=rlb@defaultvalue.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).