[Numpy-discussion] Scheduling the 1.7.1 and 1.8 releases
Charles R Harris
Thu Apr 11 11:52:27 CDT 2013
On Thu, Apr 11, 2013 at 10:12 AM, Nathaniel Smith <email@example.com> wrote:
> On 11 Apr 2013 15:29, "Charles R Harris" <firstname.lastname@example.org>
> > On Thu, Apr 11, 2013 at 4:32 AM, Sebastian Berg <
> email@example.com> wrote:
> >> On Wed, 2013-03-06 at 11:43 -0700, Charles R Harris wrote:
> >> > Hi All,
> >> >
> >> <snip>
> >> > The development branch has been accumulating stuff since last summer,
> >> > I suggest we look to get it out in May, branching at the end of this
> >> > month.
> >> Hey,
> >> maybe it is a bit early, but I was wondering. What are the things that
> >> should be done before branching? Most of the blockers should be
> >> resolved? I think the largest of that are maybe the deprecations (but
> >> since 1.7.0 is not too long ago many of them maybe don't need touching).
> >> Aside from that, I think these are lurking/in-progress:
> >> Fix the piled up mapping.c things:
> >> * This means resolving https://github.com/numpy/numpy/pull/436 .
> >> It will be even worse now, but maybe at least most of it can
> >> be put in without too much work?
> >> * After that, non-integer deprecations should be done fully before
> >> 1.8. I think, but these need to change mapping.c too (the
> >> most work is probably the tests...):
> >> - https://github.com/numpy/numpy/pull/2891
> >> - https://github.com/numpy/numpy/pull/2825
> >> * (https://github.com/numpy/numpy/pull/2701)
> >> Are the 2to3 fixers supposed to be finished for 1.8? If yes there is
> >> probably no point in thinking about branching, etc. since back porting
> >> them all is just pain.
> > There is no milestone for the 2to3 stuff, although I expect it will be
> done by the end of April.
> Will releasing 1.8 with these partially applied cause any issues that you
> can think of? (Like making later 1.8.1 backports easier or harder?) I guess
> we haven't noticed any problems backporting 1.7 changes yet, so hopefully
> it doesn't matter?
I don't think they should cause problems unless they depend the presence of
methods not present in 2.4 and 2.5, but that only affects 1.7. It is hard
to say what things will cause problems in advance, but I suspect most
things won't be difficult. If the ws_comma fixer is run and committed after
1.8 is released, there might be cherry-picking problems that would make
backports a bit more work. There are also a couple of fixes yet to go in
that involve version dependent imports, memoryview/buffer in particular,
that would be a good to have in 1.8.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the NumPy-Discussion