<br><br><div class="gmail_quote">On Wed, Jun 27, 2012 at 1:45 PM, Charles R Harris <span dir="ltr"><<a href="mailto:charlesr.harris@gmail.com" target="_blank">charlesr.harris@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br><br><div class="gmail_quote"><div class="im">On Tue, Jun 26, 2012 at 11:08 PM, Travis Oliphant <span dir="ltr"><<a href="mailto:travis@continuum.io" target="_blank">travis@continuum.io</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
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.<br>
<br>
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<br>
<br>
(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 <a href="mailto:numfocus@googlegroups.com" target="_blank">numfocus@googlegroups.com</a> if you are interested in helping with that effort).<br>
<br>
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.<br>
<br>
Let me know if there are any concerns about this updated schedule.<br>
<br></blockquote></div><div><br>That schedule sounds good to me.<br></div></div></blockquote><div><br>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. <br>
</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div class="gmail_quote"><div>I thought Nathaniel did excellent work in getting tox and Travis CI started up. Kudos there.<br>
<br></div></div></blockquote><div>Seconded. It's already quite useful. <br><br>Ralf<br><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div class="gmail_quote"><div>Chuck <br></div></div>
<br>_______________________________________________<br>
NumPy-Discussion mailing list<br>
<a href="mailto:NumPy-Discussion@scipy.org">NumPy-Discussion@scipy.org</a><br>
<a href="http://mail.scipy.org/mailman/listinfo/numpy-discussion" target="_blank">http://mail.scipy.org/mailman/listinfo/numpy-discussion</a><br>
<br></blockquote></div><br>