From: Neil Jerram <neil@ossau.uklinux.net>
To: Andy Wingo <wingo@pobox.com>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: release update
Date: Wed, 17 Jun 2009 23:46:50 +0100 [thread overview]
Message-ID: <87ws7acwbp.fsf@arudy.ossau.uklinux.net> (raw)
In-Reply-To: <m3d492a52z.fsf@pobox.com> (Andy Wingo's message of "Thu\, 18 Jun 2009 00\:05\:56 +0200")
Andy Wingo <wingo@pobox.com> writes:
> Hey Guilers,
Hi Andy!
> I didn't push anything specific regarding a freeze, but in practice
> since we're so few, we've been great at just putting in release-worthy
> fixes :)
>
> I would say that we are definitely on track for a 1.9 on the 19th.
Agreed.
> I have a list of things to add to the NEWS, which I'm appending to
> this mail just to give some scope -- the list only goes back to
> September of last year, when it really needs to go back to May or so
> when I started work on the VM, but it's close to complete WRT what I
> need to add.
>
> Please add on any missing points. Note that the 1.9 release notes will
> become the 2.0 release notes, I think; over the next few months we will
> be editing them, adding and removing things, so that readers for the 2.0
> release will understand what it is we've been up to over the last few
> years.
>
> One question is that I've been calling this thing 1.9.1 under the
> assumption that we made a 1.9.0; but that does not seem to be the case.
> Should this one be 1.9.0 or 1.9.1?
I think either is good. (The only other factor that occurs to me is a
very silly one, namely that thus far we have got away with being able
to use string<? to compare Guile versions! If we ever reached 1.9.10
(or 1.8.10, for that matter), that would no longer work.)
> OK, enough rambling. I have a plane flight tomorrow in which to write
> proper NEWS entries, after which hopefully all will be set for a release
> on Friday.
Some notes/queries on a few of your notes...
> no more currying
I thought that was unintentional, and have it on my todo list as a
bug. Is it actually intentional?
> more robust threading support.
Does this mean SRFI-18? "more robust" isn't quite right for that,
IMO; I'd say "more sophisticated API" or something.
> srfi-18
Oh, maybe not then :-)
I also made a checklist, here:
http://article.gmane.org/gmane.lisp.guile.devel/7971
My target, though, is to make sure this is all well covered in NEWS by
the time we get to the actual 2.0. I'm not very concerned about NEWS
being incomplete during the 1.9.x prereleases.
Regards,
Neil
next prev parent reply other threads:[~2009-06-17 22:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-17 22:05 release update Andy Wingo
2009-06-17 22:46 ` Neil Jerram [this message]
2009-06-18 21:01 ` Ludovic Courtès
2009-06-20 11:00 ` Andy Wingo
2009-06-20 13:34 ` Neil Jerram
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=87ws7acwbp.fsf@arudy.ossau.uklinux.net \
--to=neil@ossau.uklinux.net \
--cc=guile-devel@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).