On Wed, Mar 6, 2013 at 9:52 PM, Ralf Gommers
On Wed, Mar 6, 2013 at 9:06 PM, Nathaniel Smith
wrote: On Wed, Mar 6, 2013 at 6:43 PM, Charles R Harris
wrote: Hi All,
There are now some 14 non-merge commits in the 1.7.x branch including the critical diagonal leak fix. I think there is maybe one more critical backport and perhaps several low priority fixes, documentation and such, but I think we should start up the release process with a goal of getting 1.7.1 out by the middle of April.
What's the critical backport you're thinking of? This last shows just two backport PRs waiting to be merged, one trivial one that I just submitted, the other that needs a tweak but won't take long: https://github.com/numpy/numpy/issues?milestone=27&page=1&state=open But I agree, basically we should merge those two (today?) and then release the first RC as soon as Ondrej has a moment to do so...
I added issue 2999, which I think should be taken along. Other than that, +1 for a quick release.
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.
I would say "let's fix the blockers and then branch as soon as Ondrej has time to do it", but in practice I suspect this comes out the same as what you just said :-). I just pruned the list of blockers; here's what we've got: https://github.com/numpy/numpy/issues?milestone=1&page=1&state=open
It looks like we're not doing so well with setting Milestones correctly. Only 4 closed issues for 1.8....
Release quickly after 1.7.1 sounds good.
I hope to finish the rest of issues for 1.7.1 today or tomorrow. Should I release 1.7.1rc1 first? I think that makes sense, just to be sure, right? Ondrej