Discussion of Numerical Python

Travis Oliphant | 27 Jun 2012 07:08

NumPy 1.7 release plans

In my enthusiasm of finding someone to help with the release of NumPy 1.7 and my desire to get something
released by the SciPy conference, I was hasty and didn't gather enough feedback from others about the
release of NumPy 1.7. I'm sorry about that.

I would like to get NumPy 1.7 out the door as quickly as we can *and* make sure it is as well tested as we can --- in
fact I'm hoping we can also use this opportunity to setup a Continuous Integration system for NumPy that
will essentially extend NumPy's testing infrastructure and make it easier to do releases in the future.
Ondrej, the author of SymPy, has agreed to help on the both the release and the Continuous Integration
side. Ideally we would also start producing a code coverage report and a vbench report for NumPy as well.
This is much more likely to happen if there are other people willing to pictch in

(By the way, one of the goals of NumFOCUS is to provide Continuous Integration and code coverage resources
to all of the Scientific Python projects as funds and community resources become available --- please
email numfocus <at> googlegroups.com if you are interested in helping with that effort).

So, I would propose a code-freeze by July 13th with a beta release of NumPy 1.7 by July 17th. We will work to get
that beta release actively tested by as many projects as possible, leading to a release candidate by July
31. If all goes well I could imagine a release by August 14. If we need to make another release candidate,
then we can do that August 14th and push the release to August 28th.

Let me know if there are any concerns about this updated schedule.

Best regards,

-Travis

headers

Charles R Harris | 27 Jun 2012 13:45

Re: NumPy 1.7 release plans

On Tue, Jun 26, 2012 at 11:08 PM, Travis Oliphant <travis <at> continuum.io> wrote:

In my enthusiasm of finding someone to help with the release of NumPy 1.7 and my desire to get something released by the SciPy conference, I was hasty and didn't gather enough feedback from others about the release of NumPy 1.7. I'm sorry about that.

I would like to get NumPy 1.7 out the door as quickly as we can *and* make sure it is as well tested as we can --- in fact I'm hoping we can also use this opportunity to setup a Continuous Integration system for NumPy that will essentially extend NumPy's testing infrastructure and make it easier to do releases in the future. Ondrej, the author of SymPy, has agreed to help on the both the release and the Continuous Integration side. Ideally we would also start producing a code coverage report and a vbench report for NumPy as well. This is much more likely to happen if there are other people willing to pictch in

(By the way, one of the goals of NumFOCUS is to provide Continuous Integration and code coverage resources to all of the Scientific Python projects as funds and community resources become available --- please email numfocus <at> googlegroups.com if you are interested in helping with that effort).

So, I would propose a code-freeze by July 13th with a beta release of NumPy 1.7 by July 17th. We will work to get that beta release actively tested by as many projects as possible, leading to a release candidate by July 31. If all goes well I could imagine a release by August 14. If we need to make another release candidate, then we can do that August 14th and push the release to August 28th.

Let me know if there are any concerns about this updated schedule.

That schedule sounds good to me.

I thought Nathaniel did excellent work in getting tox and Travis CI started up. Kudos there.

Chuck

_______________________________________________
NumPy-Discussion mailing list
NumPy-Discussion <at> scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion

headers

Travis Oliphant | 27 Jun 2012 14:28

Re: NumPy 1.7 release plans

Great. Yes, the Travis-CI stuff looks great. There are a lot of good CI things happening on a lot of fronts.

It is encouraging to see.

It would be good to consolidate them --- or at least have a place to go to look at output from many of them.

Travis

Travis Oliphant

(on a mobile)

512-826-7480

On Jun 27, 2012, at 6:45 AM, Charles R Harris <charlesr.harris <at> gmail.com> wrote:

On Tue, Jun 26, 2012 at 11:08 PM, Travis Oliphant <travis <at> continuum.io> wrote:
In my enthusiasm of finding someone to help with the release of NumPy 1.7 and my desire to get something released by the SciPy conference, I was hasty and didn't gather enough feedback from others about the release of NumPy 1.7. I'm sorry about that.

I would like to get NumPy 1.7 out the door as quickly as we can *and* make sure it is as well tested as we can --- in fact I'm hoping we can also use this opportunity to setup a Continuous Integration system for NumPy that will essentially extend NumPy's testing infrastructure and make it easier to do releases in the future. Ondrej, the author of SymPy, has agreed to help on the both the release and the Continuous Integration side. Ideally we would also start producing a code coverage report and a vbench report for NumPy as well. This is much more likely to happen if there are other people willing to pictch in

(By the way, one of the goals of NumFOCUS is to provide Continuous Integration and code coverage resources to all of the Scientific Python projects as funds and community resources become available --- please email numfocus <at> googlegroups.com if you are interested in helping with that effort).

So, I would propose a code-freeze by July 13th with a beta release of NumPy 1.7 by July 17th. We will work to get that beta release actively tested by as many projects as possible, leading to a release candidate by July 31. If all goes well I could imagine a release by August 14. If we need to make another release candidate, then we can do that August 14th and push the release to August 28th.

Let me know if there are any concerns about this updated schedule.

That schedule sounds good to me.

I thought Nathaniel did excellent work in getting tox and Travis CI started up. Kudos there.

Chuck

_______________________________________________
NumPy-Discussion mailing list
NumPy-Discussion <at> scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion

_______________________________________________
NumPy-Discussion mailing list
NumPy-Discussion <at> scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion

headers

Ralf Gommers | 27 Jun 2012 22:51

Re: NumPy 1.7 release plans

On Wed, Jun 27, 2012 at 1:45 PM, Charles R Harris <charlesr.harris <at> gmail.com> wrote:

On Tue, Jun 26, 2012 at 11:08 PM, Travis Oliphant <travis <at> continuum.io> wrote:
In my enthusiasm of finding someone to help with the release of NumPy 1.7 and my desire to get something released by the SciPy conference, I was hasty and didn't gather enough feedback from others about the release of NumPy 1.7. I'm sorry about that.

I would like to get NumPy 1.7 out the door as quickly as we can *and* make sure it is as well tested as we can --- in fact I'm hoping we can also use this opportunity to setup a Continuous Integration system for NumPy that will essentially extend NumPy's testing infrastructure and make it easier to do releases in the future. Ondrej, the author of SymPy, has agreed to help on the both the release and the Continuous Integration side. Ideally we would also start producing a code coverage report and a vbench report for NumPy as well. This is much more likely to happen if there are other people willing to pictch in

(By the way, one of the goals of NumFOCUS is to provide Continuous Integration and code coverage resources to all of the Scientific Python projects as funds and community resources become available --- please email numfocus <at> googlegroups.com if you are interested in helping with that effort).

So, I would propose a code-freeze by July 13th with a beta release of NumPy 1.7 by July 17th. We will work to get that beta release actively tested by as many projects as possible, leading to a release candidate by July 31. If all goes well I could imagine a release by August 14. If we need to make another release candidate, then we can do that August 14th and push the release to August 28th.

Let me know if there are any concerns about this updated schedule.

That schedule sounds good to me.

Sounds good to me too. If no one else has gotten around to it by then, I'll make some time to merge the wiki doc edits the week before the 13th.

I thought Nathaniel did excellent work in getting tox and Travis CI started up. Kudos there.

Seconded. It's already quite useful.

Ralf

Chuck

_______________________________________________
NumPy-Discussion mailing list
NumPy-Discussion <at> scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion

_______________________________________________
NumPy-Discussion mailing list
NumPy-Discussion <at> scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion