Dear all, I have just tagged Flint 2.6.0-rc1 on GitHub [1], where tarballs are now available to download and try out.
If there are no further bug reports by this Friday 29 May 2020 the final release of flint-2.6.0 will be made. Please report bugs on our GitHub issues and successful builds here. This is now a final opportunity for everyone, including end users, to report any issues before the final release (hopefully) on Friday. Note that Flint now has new online sphinx documentation [3]. Contributors have been updated on our website [4], however we will acknowledge contributors to this release when the final release announcement is made on Friday and final release tarballs are put on the website. Please note that the soname will not be incremented for the final release. It has already been incremented for 2.6.0 in anticipation of the release. The only tasks that remain for the release are: * further updating of our website * Windows MSVC solution file documentation * release announcement Please note that the flint-2.5 branch in our repository is now defunct. All backporting from trunk will now occur on flint-2.6. Bill. [1] https://github.com/wbhart/flint2/releases/tag/2.6.0-rc1 [2] https://github.com/wbhart/flint2/issues [3] http://flintlib.org/doc/ [4] http://flintlib.org/authors.html -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/CAB0xFns5AumRwRV0eUtv_iLZDPwiNO_zCP9O%3D8ZJ6u5ZJ4Px1Q%40mail.gmail.com.
