Yep, this will only affect the Windows build, so no need for a full round of testing. Simply do a sample linux build on sage.math just to make sure something unexpected didn't happen and then call for a round of Windows testing.
It should be called 2.1.1 which means running the setversion script again etc. Bill. On 9 June 2010 18:02, Cactus <[email protected]> wrote: > > > On Jun 9, 5:49 pm, Minh Nguyen <[email protected]> wrote: >> Hi Brian, >> >> On Thu, Jun 10, 2010 at 2:19 AM, Cactus <[email protected]> wrote: >> >> <SNIP> >> >> > I am afraid, Minh, that this is serious enough to require either a re- >> > release of MPIR 2.1.0 or a step release. >> >> How about a quick MPIR 2.1.1 bug fix release? Just tell me when you're >> done with fixing the above bug, and I'll announce an RC for testing. >> When things looks OK, we could announce an MPIR 2.1.1 bug fix release. >> >> I have updated the list of known issues on the MPIR website. >> >> -- >> Regards >> Minh Van Nguyen > > Its all done in SVN now. I have added better Python detection to the > command line build scripts. > > Only Windows x64 builds for K8 and K10 need testing so a short RC > cycle should be fine. > > Sorry for the extra work. And thanks to Case for finding this bug > quickly. > > Brian > > -- > You received this message because you are subscribed to the Google Groups > "mpir-devel" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/mpir-devel?hl=en. > > -- You received this message because you are subscribed to the Google Groups "mpir-devel" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/mpir-devel?hl=en.
