From: Andy Wingo <wingo@pobox.com>
To: Mark H Weaver <mhw@netris.org>
Cc: guile-devel@gnu.org
Subject: Re: 2.0.x branched!
Date: Sat, 19 Feb 2011 14:16:31 +0100 [thread overview]
Message-ID: <m3aahs17ww.fsf@unquote.localdomain> (raw)
In-Reply-To: <87k4gw2929.fsf@netris.org> (Mark H. Weaver's message of "Fri, 18 Feb 2011 18:54:06 -0500")
Hi Mark,
On Sat 19 Feb 2011 00:54, Mark H Weaver <mhw@netris.org> writes:
> Andy Wingo <wingo@pobox.com> writes:
>> Compatible changes on 2.0.x seem fine to me; we should live in 2.0.x
>> for a year or two I think.
>
> What do you mean by "live in 2.0.x"? Does this mean that we should
> avoid working on deeper changes to Guile for the next year or two?
I expressed myself poorly there. What I meant was that we should aim
for a 2.2.0 release within a year ot two; and that in the meantime we
should focus on consolidating our gains with the 2.0 series. We need to
get 2.0 into the distros, to see wider use of 2.0, and that will take a
little time.
I did not mean to discourage work on master, no. I actually meant to
encourage those changes that are compatible with 2.0 to go on the
stable-2.0 branch.
> What does this mean for my pending patches that support
> arbitrary-precision floats and GOOPS-based numeric types?
They would go on master, because they would probably be incompatible
with 2.0.0. Speaking of which, can you ask to be added to the Guile
group on Savannah? That will allow you to commit directly. I would
like for you to continue to mail your patches to the list before
pushing, just to make sure we're all on the same page. If everything
goes well this would become less necessary over time.
> It's too bad, because I'm all fired up to do a bunch of work on guile,
> not just on numerics but other stuff too. Bad timing, I guess.
Let's hack :) I plan on being a little less responsive over the next
couple months than I have been recently, so patience remains a virtue ;)
But there's loads of things to do, and your careful and courageous work
has been much appreciated!
Cheers,
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2011-02-19 13:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-15 15:50 2.0.x branched! Ludovic Courtès
2011-02-18 20:37 ` Neil Jerram
2011-02-18 23:17 ` Andy Wingo
2011-02-18 23:25 ` Neil Jerram
2011-02-18 23:54 ` Mark H Weaver
2011-02-19 13:16 ` Andy Wingo [this message]
2011-02-19 18:25 ` Mark H Weaver
2011-02-20 11:02 ` Andy Wingo
2011-02-21 20:34 ` Ludovic Courtès
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=m3aahs17ww.fsf@unquote.localdomain \
--to=wingo@pobox.com \
--cc=guile-devel@gnu.org \
--cc=mhw@netris.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).