Re: release plans and schedule

Hi Bruno,

> * Bruno Haible <[email protected]> [2017-12-03 18:49:02 +0100]:
>
> clisp now has much fewer build failures and random crashes that it had
> a year ago, and all of the "high-prority" items of my TODO list that I
> set up in February 2017 are fixed. Therefore my original plan would
> have been:
>
>   - fix remaining high-priority issues: bug 718.

I think 719 is also high-priority.
It is unconscionable that CLISP compiles its own libunistring and
libregexp on linux.
The current situation is that configure detects a good working
libunistring and sets LTLIBUNISTRING, but fails to massage it into LIBS.
However, I won't insist.

> Now it seems you (esp. Sam and Jörg) want to hack on something.

My TODO contains only LOOP.
If I cannot fix it on your schedule, you can roll back my recent changes
for the releases.
I think getting releases out should be the top priority.

> Therefore I guess we should at some point create a release branch, so
> that you can continue to hack with full speed and at the same time we
> limit the risk of breakage just before release. The precise question
> is WHEN to create this release branch.

I think we should revisit this when you are done with your
"pre-prerelease TODO" and ready to make the branch (in a week?)
At that point I will either say "LOOP is fixed" or "please create the
branch and roll back 52d209b7d29d".

Thanks!

-- 
Sam Steingold (http://sds.podval.org/) on darwin Ns 10.3.1504
http://steingoldpsychology.com http://www.childpsy.net http://jij.org
http://honestreporting.com http://no2bds.org http://camera.org
Suppose there is no empty set. Then consider the set of all empty sets.

------------------------------------------------------------------------------
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