[Numpy-discussion] Numpy 1.6 schedule (was: Numpy 2.0 schedule)

Ralf Gommers ralf.gommers@googlemail....
Fri Mar 4 00:54:55 CST 2011


On Mon, Feb 28, 2011 at 11:31 PM, Ralf Gommers
<ralf.gommers@googlemail.com> wrote:
> On Mon, Feb 28, 2011 at 10:36 PM, Bruce Southey <bsouthey@gmail.com> wrote:
>> On 02/28/2011 02:00 AM, Ralf Gommers wrote:
>>> Hi,
>>>
>>> On Fri, Jan 28, 2011 at 7:15 AM, Travis Oliphant<oliphant@enthought.com>  wrote:
>>>> The reason for a NumPy 1.6 suggestion, is that Mark (and others it would
>>>> seem) have additional work and features that do not need to wait for the
>>>> NumPy 2.0 ABI design to finalize in order to get out there.
>>>> If someone is willing to manage the release of NumPy 1.6, then it sounds
>>>> like a great idea to me.
>>> This thread ended without a conclusion a month ago. Now I think master
>>> is in a better state than a month ago for a release (py 2.4/2.5/3.x
>>> issues and segfault on OS X fixed, more testing of changes), and I
>>> have a better idea of my free time for March/April. Basically, I have
>>> a good amount of time for the next couple of weeks, and not so much at
>>> the end of March / first half of April due to an inter-continental
>>> move. But I think we can get out a beta by mid-March, and I can manage
>>> the release.
>>>
>>> I've had a look at the bug tracker, here's a list of tickets for 1.6:
>>> #1748 (blocker: regression for astype('str'))
>>> #1619 (issue with dtypes, with patch)
>>> #1749 (distutils, py 3.2)
>>> #1601 (distutils, py 3.2)
>>> #1622 (Solaris segfault, with patch)
>>> #1713 (Solaris segfault)
>>> #1631 (Solaris segfault)

The distutils tickets are resolved.

>>> Proposed schedule:
>>> March 15: beta 1
>>> March 28: rc 1
>>> April 17: rc 2 (if needed)
>>> April 24: final release

Any comments on the schedule or tickets?

Before the first beta can be released I think #1748 should be fixed.
Before the first RC the Solaris segfaults should be investigated, and
documentation for the new iterator (Python docstrings and C API docs)
and datetime should be written.

Also, some testing on 64-bit Windows would be great, that usually
turns up new issues so the sooner the better.

Ralf


More information about the NumPy-Discussion mailing list