Thanks Ralf and Nathan, I have put high priority on the issues that need to be fixed before the rc1. There are now 4 issues:
https://github.com/numpy/numpy/issues?labels=priority%3A+high&milestone=3&page=1&state=open I am working on the mingw one, as that one is the most difficult. Ralf (or anyone else), do you know how to fix this one: https://github.com/numpy/numpy/issues/438 I am not very familiar with this part of numpy, so maybe you know how to document it well. The sooner we can fix these 4 issues, the sooner we can release. Ondrej On Sun, Dec 16, 2012 at 1:49 AM, Ralf Gommers <ralf.gomm...@gmail.com> wrote: > > > > On Sun, Dec 16, 2012 at 3:17 AM, Nathaniel Smith <n...@pobox.com> wrote: >> >> #294 is a regression, so probably should be considered release critical. I >> can't tell if #2750 is a real problem or not. #378 looks serious, but afaict >> has actually been fixed even though the bug is still marked open? At least >> fixed in 1.7.x? >> >> On 15 Dec 2012 23:52, "Ondřej Čertík" <ondrej.cer...@gmail.com> wrote: >>> >>> Hi, >>> >>> If you go to the issues for 1.7 and click "high priority": >>> >>> >>> https://github.com/numpy/numpy/issues?labels=priority%3A+high&milestone=3&state=open >>> >>> you will see 3 issues as of right now. Two of those have PR attached. >>> It's been a lot of work >>> to get to this point and I'd like to thank all of you for helping out >>> with the issues. >>> >>> >>> In particular, I have just fixed a very annoying segfault (#2738) in the >>> PR: >>> >>> https://github.com/numpy/numpy/pull/2831 >>> >>> If you can review that one carefully, that would be highly >>> appreciated. The more people the better, >>> it's a reference counting issue and since this would go into the 1.7 >>> release and it's in the core of numpy, >>> I want to make sure that it's correct. >>> >>> So the last high priority issue is: >>> >>> https://github.com/numpy/numpy/issues/568 >>> >>> and that's the one I will be concentrating on now. After it's fixed, I >>> think we are ready to release the rc1. >>> >>> There are more open issues (that are not "high priority"): >>> >>> >>> https://github.com/numpy/numpy/issues?labels=&milestone=3&page=1&state=open >>> >>> But I don't think we should delay the release any longer because of >>> them. Let me know if there >>> are any objections. Of course, if you attach a PR fixing any of those, >>> we'll merge it. > > > Properly documenting .base (gh-2737) and casting rules (gh-561) changes > should be finished before rc1. I agree that the Debian issues all shouldn't > block the release. > > Ralf > > > _______________________________________________ > NumPy-Discussion mailing list > NumPy-Discussion@scipy.org > http://mail.scipy.org/mailman/listinfo/numpy-discussion > _______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
