From: Andy Wingo <wingo@pobox.com>
To: guile-devel <guile-devel@gnu.org>
Subject: release status
Date: Sun, 15 Nov 2009 21:35:37 +0100 [thread overview]
Message-ID: <m3639bo7ae.fsf@pobox.com> (raw)
Hi,
Quick note from a tired hacker :) I had a lovely time at the GNU
hacker's meeting in Sweden, and just got back today. I'm sure Ludovic
has similar positive reports. The deal for Guile though is that we
didn't get enough time to hack, and there is an optargs bug (relative to
past ice-9 behavior). So for that reason we're punting the release to
Tuesday the 17th.
So tomorrow, to fix that bug, and to write the NEWS. The test suite does
have two cases that are known to fail. Otherwise, any error reports are
appreciated, as always.
Cheers,
Andy
--
http://wingolog.org/
reply other threads:[~2009-11-15 20:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=m3639bo7ae.fsf@pobox.com \
--to=wingo@pobox.com \
--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).