[Numpy-discussion] Code Freeze for NumPy 1.7

Russell E. Owen rowen@uw....
Mon Jul 16 16:28:22 CDT 2012


In article <1342393528.28368.3.camel@esdceeprjpstudent1.mit.edu>,
 Paul Natsuo Kishimoto <mail@paul.kishimoto.name> wrote:

> On Sat, 2012-07-14 at 17:45 -0500, Travis Oliphant wrote:
> > Hey all, 
> > 
> > We are nearing a code-freeze for NumPy 1.7.   Are there any
> > last-minute changes people are wanting to push into NumPy 1.7?  We
> > should discuss them as soon as possible. 
> > 
> > I'm proposing a code-freeze at midnight UTC on July 18th (7:00pm CDT
> > on July 17th).   This will allow the creation of beta releases of
> > NumPy on the 18th of July. This is a few days later than originally
> > hoped for --- largely due to unexpected travel schedules of Ondrej and
> > I, but it does give people a few more days to get patches in.  Of
> > course, we will be able to apply bug-fixes to the 1.7.x branch once
> > the tag is made. 
> > 
> > If you have a pull-request that is not yet applied and would like to
> > discuss it for inclusion, the time to do it is now. 
> > 
> > Best, 
> > 
> > -Travis
> 
> 
> Bump for: https://github.com/numpy/numpy/pull/351
> 
> 
> As requested by njsmith, I gave a more detailed explanation and asked
> the list for input at:
> http://www.mail-archive.com/numpy-discussion@scipy.org/msg38306.html
> 
> There was one qualified negative reply and nothing (yet) further. I'd
> appreciate if some other devs could weigh in.

My personal opinion is that the improvement is not sufficient to justify 
breaking backword compatibility.

-- Russell



More information about the NumPy-Discussion mailing list