[Numpy-discussion] 1.7.0 release

[Ondřej Čertík]

On Mon, Nov 12, 2012 at 3:47 PM, Charles R Harris
<charlesr.harris at gmail.com> wrote:
>
>
> On Mon, Nov 12, 2012 at 3:27 PM, Ondřej Čertík <ondrej.certik at gmail.com>
> wrote:
>>
>> Hi,
>>
>> On Mon, Nov 5, 2012 at 11:33 PM, Travis Oliphant <travis at continuum.io>
>> wrote:
>> > Hey all,
>> >
>> > Ondrej has been tied up finishing his PhD for the past several weeks.
>> > He is defending his work shortly and should be available to continue to help
>> > with the 1.7.0 release around the first of December.    He and I have been
>> > in contact during this process, and I've been helping where I can.
>> > Fortunately, other NumPy developers have been active closing tickets and
>> > reviewing pull requests which has helped the process substantially.
>> >
>> > The release has taken us longer than we expected, but I'm really glad
>> > that we've received the bug-reports and issues that we have seen because it
>> > will help the 1.7.0 release be a more stable series.   Also, the merging of
>> > the Trac issues with Git has exposed over-looked problems as well and will
>> > hopefully encourage more Git-focused participation by users.
>> >
>> > We are targeting getting the final release of 1.7.0 out by mid December
>> > (based on Ondrej's availability).   But, I would like to find out which
>> > issues are seen as blockers by people on this list.   I think most of the
>> > issues that I had as blockers have been resolved.    If there are no more
>> > remaining blockers, then we may be able to accelerate the final release of
>> > 1.7.0 to just after Thanksgiving.
>>
>>
>>
>> I successfully defended my Ph.D. thesis last Thursday, I just need to
>> do some changes to it and submit it and I am done.
>> So I started to work on the release again (my apologies that it got
>> delayed, I had to devote my full attention to finishing my school
>> first).
>>
>> Here is a list of issues that need to be fixed before the release:
>>
>> https://github.com/numpy/numpy/issues?milestone=3&state=open
>>
>> If anyone wants to help, we just need to get through them and submit a
>> PR for each, or close it if it doesn't apply anymore.
>> This is what I am doing now.
>>
>
> Concrats. There are some commits already due for backports. Do you want to
> do that, or will it be OK for others to do it? Another possibility would be
> to open new PR's for the backports and tag them as 1.7.0.

I'll be happy to do that. If you know which commits are those, let me know.
I actually like to open a PR just for the backports as well, to see if tests
pass and to have more eyes look on it to minimize mistakes.

Ondrej