unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Andy Wingo <wingo@pobox.com>
To: ludo@gnu.org (Ludovic Courtès)
Cc: guile-devel@gnu.org
Subject: Re: Plan for the next release
Date: Sun, 14 Feb 2010 16:54:04 +0100	[thread overview]
Message-ID: <m3y6ivak4j.fsf@pobox.com> (raw)
In-Reply-To: <87pr47ub92.fsf@gnu.org> ("Ludovic Courtès"'s message of "Sun, 14 Feb 2010 15:45:29 +0100")

Howdy,

On Sun 14 Feb 2010 15:45, ludo@gnu.org (Ludovic Courtès) writes:

> Andy Wingo <wingo@pobox.com> writes:
>
>> Regarding the release... I have no thoughts. Perhaps I should prepare
>> the NEWS, and we get a release out the door this week, then the next one
>> will have catch/throw nicely integrated, and at that point I'll be
>> mostly happy for 2.0. Thoughts?
>
> I think the main focus for the two months preceding 2.0 should be:
>
>   0. Licensing and copyright (‘pmatch’, etc.). [*]
>
>   1. Portability fixes.
>
>   2. Backward-compatibility fixes.
>
>   3. Documented anything new and undocumented.
>
>   4. Bug hunting.

Agreed. Let me add: full parallel-installability (currently our support
is only partial), so that a 2.2 can come out without affecting 2.0
installations. (e.g. putting libguile.h in a versioned subdir, and have
pkg-config add -I$includedir/guile-2.0/ to the CFLAGS)

> If you think catch/throw on delimited continuations may be ready in a
> couple of weeks, and that it’s the last big feature you have in mind for
> 2.0, then that’s fine with me.  :-)  Otherwise, I’d be in favor of
> delaying 2.0 as long as needed so we can work on the above points.

OK. I think I can get it in, yes.

> Note that I’m in favor of shorter release cycles, which means 2.2
> shouldn’t be decades away from 2.0.  We could even create a 2.2 branch
> one of these days for things we want to play with but that won’t be
> ready for prime time until some time.

This sounds great to me.

Cheers,

Andy
-- 
http://wingolog.org/




  reply	other threads:[~2010-02-14 15:54 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-14 12:33 catch, throw, prompt, control, fluids, garbage collection Andy Wingo
2010-02-14 14:32 ` Fluids Ludovic Courtès
2010-02-14 15:50   ` Fluids Andy Wingo
2010-02-14 19:09     ` Fluids Ken Raeburn
2010-03-02 23:52   ` Fluids Ludovic Courtès
2010-03-03 12:29     ` Fluids Andy Wingo
2010-03-03 13:09       ` Fluids Ludovic Courtès
2010-03-05 17:24       ` Fluids Ludovic Courtès
2010-02-14 14:45 ` Plan for the next release Ludovic Courtès
2010-02-14 15:54   ` Andy Wingo [this message]
2010-02-15 22:07 ` catch, throw, prompt, control, fluids, garbage collection Andy Wingo
2010-02-18 22:35   ` Andy Wingo
2010-02-25  0:00     ` Andy Wingo
2010-02-26 12:27       ` Andy Wingo
2010-02-28 22:16         ` Neil Jerram
2010-07-17 10:15           ` Andy Wingo

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=m3y6ivak4j.fsf@pobox.com \
    --to=wingo@pobox.com \
    --cc=guile-devel@gnu.org \
    --cc=ludo@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).