[Chicken-hackers] Should we make a 4.12 release?

[Peter Bex]

Hi all,

I'm wondering whether we should make a 4.12 release candidate.  There
are a handful of very bad bugs (#1317, #1337, #1336) and 3 CVEs that
have been fixed.

There are still 3 patches waiting (1 bugfix for #1144), so I'd prefer
to wait until after they've been applied.

After my patch for #1144 is applied, there will be 4 open bugs left:
https://bugs.call-cc.org/query?status=assigned&status=new&status=accepted&status=reopened&group=status&milestone=4.12.0

I'm not sure what to do about #1293.  We don't have a simple way
of assigning unique object IDs, so some objects will "notice" they
get moved by the GC and all objects will notice when they're mutated.

I proposed a patch for #1294, but Felix didn't like it.  It's a tricky
thing to fix otherwise, so Felix, unless you know how to fix this, we
probably are better off postponing it.

Mario, what is the final word on #1298?  Your last comment seems to
indicate that this should maybe be closed "wontfix"?

Christian was unable to check whether #1107 has been fixed with the
latest GCC, because the port was broken.  It's just a warning which
has probably been in there forever.  We could add the --std switch,
but I have no idea about the consequences, which could be pretty
far-reaching for eggs (or could make no difference at all).

Cheers,
Peter

signature.asc
Description: Digital signature