From: Rob Browning <rlb@defaultvalue.org>
Subject: Preparing 1.6.1.
Date: Mon, 02 Sep 2002 17:21:04 -0500 [thread overview]
Message-ID: <87ptvw3uen.fsf@raven.i.defaultvalue.org> (raw)
Just a heads up -- as far as I can see, we haven't had any
showstopping bugs crop up in 1.5.8, so unless there's something I've
missed, it's time for the 1.6.1 release.
Comments? Anything that can't wait for 1.6.2? If not, I'll be
preparing/checking the release as I have time over the next day or
two. For anyone with spare time, I'd still be happy to accept any
NEWS revisions or improvements, or other documentation fixes, but
please coordinate with me so you don't commit something after I've
tagged/built the release.
Thanks
--
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-09-02 22:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-02 22:21 Rob Browning [this message]
2002-09-02 23:51 ` Preparing 1.6.1 Han-Wen Nienhuys
2002-09-03 0:52 ` Rob Browning
2002-09-03 16:32 ` Marius Vollmer
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=87ptvw3uen.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).