I thought now might be a good time to give an update on the status of the MPIR project.
Brian Gladman (the Windows MSVC "maintainer") and William Hart (the Linux/OSX "maintainer") have decided to separate the Windows MSVC development from the Linux/OSX development. There will be separate repositories for this. Currently, there are no maintainers for other platforms, and only x86_64 is targeted. In order to ensure continuity of MPIR for all projects that continue to use it, we have decided to revert to a continuously maintained community repository, instead of issuing official releases. We will no longer be maintainers, but curators. This means our sole job is to ensure no garbage ends up in the repository, the performance and stability is not degraded on targeted platforms, pull requests are only accepted if continuous integration passes, and to offer assistance to serious developers as time permits. We will no longer offer assistance to ordinary users of MPIR. I have brought the Linux/OSX repository into a workable state after recent efforts of Dima Pasechnik, Brian Gladman and others, and MSVC solution files have been removed. A number of improvements that have been in the pipe for a long time have been finally merged, and a few well-known bugs have been fixed. The continuous integration passes all tests. I have also updated the website. The most important thing is to ensure the integrity of the MPIR repository and allow projects that currently use MPIR to continue to do so, and that patches can be contributed by anyone across the entire community. The biggest issue going forward will be packaging. Most distros will want to see official releases. As this is simply too much work for two "curators", there will need to be a discussion on how this can be achieved. I intend to make a more complete announcement in say a month about how exactly everything is going to work. The immediate takeaway is that MPIR is *not* being actively developed, but we accept patches (*) from the community at large and review them. I hope everyone will understand that we do not have time to have extensive discussions on this that aren't about actual improvements of the code in the repository. --- (*) Unfortunately we do not have CI resources to test new assembly code, therefore this can only be contributed by individuals that we can verify have the necessary technical skills. -- 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 post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
