[Numpy-discussion] Status of the 1.7 release
Sun Dec 16 03:49:08 CST 2012
On Sun, Dec 16, 2012 at 3:17 AM, Nathaniel Smith <email@example.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" <firstname.lastname@example.org> wrote:
>> If you go to the issues for 1.7 and click "high priority":
>> 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
>> 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:
>> 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"):
>> 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.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the NumPy-Discussion