From: Arne Babenhauserheide <arne_bab@web.de>
To: Andy Wingo <wingo@pobox.com>
Cc: guile-user@gnu.org, guile-devel@gnu.org
Subject: Re: GNU Guile 2.1.7 released (beta)
Date: Fri, 24 Feb 2017 18:46:05 +0100 [thread overview]
Message-ID: <87k28fmqhu.fsf@web.de> (raw)
In-Reply-To: <87tw7kviu6.fsf@pobox.com>
[-- Attachment #1: Type: text/plain, Size: 807 bytes --]
Andy Wingo <wingo@pobox.com> writes:
> I think that the 2.1.x series is ready to go.
Nice!
> Release blocker bugs principally concern ABI. For example the foreign
> objects facility which was applied to 2.0 and 2.2 and then rolled out
> from 2.0 because maybe it's not an interface that we want to support in
> the future -- well that is still part of 2.2 and if we released today we
> would indeed have to support it. It's that kind of question.
The main strategical question I see for that is: Does anything make it
harder to complete or improve the lilypond transition to Guile 2?
Is there something which would need to be done before 2.2 which could
make it easier for lilypond developers?
Best wishes,
Arne
--
Unpolitisch sein
heißt politisch sein
ohne es zu merken
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 800 bytes --]
next prev parent reply other threads:[~2017-02-24 17:46 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-18 10:31 GNU Guile 2.1.7 released (beta) Andy Wingo
2017-02-18 14:34 ` GNU Guile 2.1.7 released (beta), SOCK_NONBLOCK Matt Wette
2017-02-21 20:58 ` Andy Wingo
2017-02-18 17:40 ` GNU Guile 2.1.7 released (beta) Matt Wette
2017-02-18 17:48 ` Matt Wette
2017-02-23 18:54 ` Andy Wingo
2017-02-23 20:04 ` Mike Gran
2017-02-23 21:06 ` Andy Wingo
2017-02-24 0:52 ` Break-when [was GNU Guile 2.1.7 released (beta)] Matt Wette
2017-02-24 14:02 ` GNU Guile 2.1.7 released (beta) Andy Wingo
2017-02-24 17:46 ` Arne Babenhauserheide [this message]
2017-02-26 17:57 ` Andy Wingo
2017-02-27 19:32 ` Mike Gran
2017-02-27 20:30 ` Andy Wingo
2017-02-27 23:00 ` Thomas Morley
2017-02-28 8:31 ` Andy Wingo
2017-03-05 16:54 ` Thomas Morley
2017-03-01 18:04 ` Arne Babenhauserheide
2017-02-28 0:04 ` David Pirotte
2017-02-28 1:49 ` Daniel Llorens
2017-03-02 20:54 ` David Pirotte
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=87k28fmqhu.fsf@web.de \
--to=arne_bab@web.de \
--cc=guile-devel@gnu.org \
--cc=guile-user@gnu.org \
--cc=wingo@pobox.com \
/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).