unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: ludo@gnu.org (Ludovic Courtès)
Cc: guile-devel@gnu.org
Subject: Re: Release time!
Date: Tue, 06 Nov 2012 00:59:49 -0500	[thread overview]
Message-ID: <87fw4ncluy.fsf@tines.lan> (raw)
In-Reply-To: <87mwyvudgz.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Mon, 05 Nov 2012 19:11:24 +0100")

ludo@gnu.org (Ludovic Courtès) writes:
> I think time has come for 2.0.7.  I suggest scheduling it for Week 48,
> WDYT?

Sounds good!

Here are the items from my TODO list that I hope to do for 2.0.7:
(and if anyone else wants to do any of these, that would be great!)

* Move docs for SRFI-9 records into the "Compound Data Types" section of
  the manual, and move docs for the older structures and records into a
  "Low-level structures" section (with big warnings on top).

* Fix thread-unsafe lazy initialization of 'scm_eval_string_in_module'.
  (and search for other similar bugs).

* Deal with the LD_LIBRARY_PATH issue.

* Make sure that curly-infix is disabled when reading elisp code.

* Fix par-map and par-for-each to use all ncores, not ncores-1.

* Fix decompile-tree-il to recognize 'case' statements properly, now
  that 'eqv?' is sometimes being optimized to 'eq?'.

and maybe:

* Figure out a way to make Guildhall modules that will be overridden by
  a matching module in core guile (if it exists).  This is important for
  SRFIs.  Ian Price's Guildhall repository contains portable
  implementions of several SRFIs that might become part of core Guile in
  the future, and the core versions should take priority.

     Mark



  parent reply	other threads:[~2012-11-06  5:59 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-05 18:11 Release time! Ludovic Courtès
2012-11-05 20:13 ` Hans Aberg
2012-11-05 21:02   ` Ludovic Courtès
2012-11-05 21:48     ` Hans Aberg
2012-11-06 18:28       ` Ludovic Courtès
2012-11-06 21:23         ` Hans Aberg
2012-11-05 20:53 ` Ludovic Courtès
2012-11-05 22:38 ` Bruce Korb
2012-11-06 18:29   ` Ludovic Courtès
2012-11-06  2:06 ` nalaginrut
2012-11-06  6:05   ` Mark H Weaver
2012-11-06 18:30   ` Ludovic Courtès
2012-11-06  5:59 ` Mark H Weaver [this message]
2012-11-06 18:41   ` Ludovic Courtès
2012-11-06 21:35     ` Ian Price
2012-11-07  0:01       ` Andreas Rottmann

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=87fw4ncluy.fsf@tines.lan \
    --to=mhw@netris.org \
    --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).