From: ludo@gnu.org (Ludovic Courtès)
To: guile-devel@gnu.org
Subject: Re: Guile 2.2 TODO
Date: Tue, 29 Oct 2013 13:27:21 +0100 [thread overview]
Message-ID: <87li1cqn2u.fsf@gnu.org> (raw)
In-Reply-To: 87y55q297k.fsf@pobox.com
Andy Wingo <wingo@pobox.com> skribis:
> On Sun 01 Sep 2013 13:03, Andy Wingo <wingo@pobox.com> writes:
[...]
>> I think that's pretty much it. Obviously it would be nice to get a lot
>> of other things into 2.2 but this is the necessary bit. I think we
>> should shoot for a 2.1.0 release around 1 December; dunno.
>
> I think we'll be ready on that date, code-wise, but documentation makes
> a 2.1.0 release much less likely -- documenting things takes time.
That’s because the doc of the VM in 2.0 put the bar very high. :-)
FWIW, I think it’s fine for an odd release series to have incomplete
documentation (especially about the internals) if that can be fixed
before the stable series comes out.
Thank you for the impressive work!
Ludo’.
prev parent reply other threads:[~2013-10-29 12:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-01 11:03 Guile 2.2 TODO Andy Wingo
2013-09-01 19:07 ` Peter TB Brett
2013-09-02 20:01 ` Andy Wingo
2013-09-14 13:48 ` Ludovic Courtès
2013-09-17 20:16 ` Andy Wingo
2013-10-03 21:27 ` Andy Wingo
2013-10-18 9:56 ` Andy Wingo
2013-10-29 12:27 ` Ludovic Courtès [this message]
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=87li1cqn2u.fsf@gnu.org \
--to=ludo@gnu.org \
--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).