Next release

[Waldek Hebisch]

Preparation for next release goes reasonably well. There
are two significant changes that I want to commit:
- preliminary routine for integration in terms of elliptic functions
- Spad implementation of polygamma.
That should be done in next few days.

So I think we should do release around June 20.

--
Waldek Hebisch

[Ralf Hemmecke]

I would still like to integrate jfricas, but I am not yet finished with
its integration into configure and Makefile.in.

Furthermore, I would like to change install.rst (and therefore INSTALL)
to include something like this:

https://hemmecke.github.io/qeta/fricasinstall.html

In particular, I would like to make it into essentially 2 sections.
(a) simple installation (binary) and
(b) from source installation,
(b1) from source distribution with pregenerated files),
(b2) from git repo.

There is also still some ideas concerning fricas.github.io in my queue,
but I can also do this after the release.

Important for me is to get jfricas (or rather hunchentoot) into the
binary distribution.

Ralf

[Waldek Hebisch]

I am affraid it is too late for this release. AFAICS including
hunchentoot means that we need to change way in which binaries are
made. This in turn means testing several build variations and
fixing possible breakage. This can be done comfortably in
parallel with other activities during 2-3 months. One month
may be enough if all goes well. But trying to do this in two
weeks is just mad rush. As I wrote doing release during summer
is incovenient for me, so trying to include jfricas in binary in
this release may delay it by 3 months. I think it is more sensible
to release now, and have new release after 3 months when issues
related to jfricas are worked out.

BTW: Best time to include new code is just after release. Some
additions are pretty safe so I am doing them late in release
cycle. But changes needed for including hunchentoot are
definitely potential risk.

--
Waldek Hebisch