From: Evan Prodromou <evan@glug.org>
Subject: Bug Reports for 1.6 Release Candidates
Date: Sat, 16 Mar 2002 12:50:59 -0600 [thread overview]
Message-ID: <87it7wz6r0.fsf@tyrell.bad-people-of-the-future.san-francisco.ca.us> (raw)
While I'm on the subject of release critical bugs: I think that the
1.6 release candidate builds need to be better advertised on the Guile
Web site. After all, this is probably the most important thing
happening with Guile right now, and it should be the most prominently
featured piece of info there.
The news of the 1.5.x releases should be on the index page, with a
prominent link to the how-to-report-a-bug page, and a link to the
current unresolved bugs list. I don't think the BUGS file, or an
HTML-munged version of such, is available anywhere on the site.
~ESP
--
Evan Prodromou
evan@glug.org
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next reply other threads:[~2002-03-16 18:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-16 18:50 Evan Prodromou [this message]
2002-03-17 3:05 ` Bug Reports for 1.6 Release Candidates 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
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=87it7wz6r0.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).