Re: release plans and schedule

Hi Sam and Jörg,

> >   - fix remaining high-priority issues: bug 718.

Done.

> 1. regexp module #691
> 2. Hopefully loop.
> My TODO contains only LOOP.
> I think 719 is also high-priority.

OK, that's clear. And many more commits have gone in since beginning of
December 2017. All this is too fresh to go into the release that everyone
is waiting for.

I'm going to put the following into the release branch:
all commits <= 16183
16185..16209
16211..16212
16214..16215
16219..16222
16224..16226
16229
16231
16234
16236
16238..16240
16242..16243
16245..16252
16254
16261
16264..16267
and the remaining asm fixes.

> I think 719 is also high-priority.
> It is unconscionable that CLISP compiles its own libunistring and
> libregexp on linux.

This can wait for 2.51.

> At that point I will either say "LOOP is fixed" or "please create the
> branch and roll back 52d209b7d29d".

I don't like to roll back on the branch (because that makes "hg annotate"
results harder to understand). Instead, I'm picking a branch point and
cherry-picking from the main branch.

Bruno


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
clisp-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/clisp-devel