This was a pretty unusual release in that officially it happened on the same day as 1.0.0. That is unlikely to ever happen again. However, I am all in favour of Jeff's suggestion.
We did do a full testing cycle for linux and we asked Brian about Windows testing, but as he had been away we didn't expect as much testing as usual there. Jeff, would you like to volunteer to offer testing on certain machines for coming release cycles? I'd like to expand our testing coverage. Sage tests MPIR on very many systems, but mostly they will be x86's. But we really ought to look into expanding our testing on Sun machines and Apple laptops for example. BTW, I am more than happy to issue a 1.1.1 to fix some issues that have been found. Certainly when Brian indicates he has fixed the Windows issues, we'll do that. The changes also need to be reflected in the 1.1 branch, but if you tell me which files are affected Brian I can move them across and issue the 1.1.1 release. Bill. 2009/4/17 Jeff Gilchrist <jeff.gilchr...@gmail.com>: > > On Fri, Apr 17, 2009 at 4:39 PM, Cactus <rieman...@googlemail.com> wrote: > >> Sadly you are right - I have not committed the subadd_n.asm file. I >> have now done this in the trunk. >> >> I am afraid that I was on holiday last week and this, combined with >> the rapid release of 1.1 after 1.0 caught me out on this one. > > I was away last week as well, not on an enjoyable holiday, but looking > after my two children who had a very bad stomach virus. One ended up > in the Children's hospital for a day too. So it looks like the > Windows issue slipped by. > > Maybe in the future before a final release is done there can be a > minimum list of systems that need tested, like at least one k8, core2 > on both UNIX and Windows systems before it can be declared final > release. That would at least ensure all the common systems have been > tested. > > Jeff. > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "mpir-devel" group. To post to this group, send email to mpir-devel@googlegroups.com To unsubscribe from this group, send email to mpir-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/mpir-devel?hl=en -~----------~----~----~----~------~----~------~--~---
