On Fri, May 31, 2013 at 11:47 PM, Charles R Harris
charlesr.har...@gmail.com wrote:
Hi All,
Most of the PR's that were mentioned as desirable for the 1.8 release have
been merged, or look to be merged in the next week or two. The current list
of
Hi All,
Most of the PR's that were mentioned as desirable for the 1.8 release have
been merged, or look to be merged in the next week or two. The current list
of
blockershttps://github.com/numpy/numpy/issues?milestone=1page=1state=opendoesn't
look to severe to me but I suspect that it is
On Thu, Apr 25, 2013 at 8:19 AM, Dave Hirschfeld
dave.hirschf...@gmail.comwrote:
Hi All,I think it is time to start the runup to the 1.8 release. I don't
know of any outstanding blockers but if anyone has a PR/issue that they
feel
needs to be in the next Numpy release now is the time to make
On Thu, Apr 25, 2013 at 11:16 AM, Charles R Harris
charlesr.har...@gmail.com wrote:
Hi All,
I think it is time to start the runup to the 1.8 release. I don't know of
any outstanding blockers but if anyone has a PR/issue that they feel needs
to be in the next Numpy release now is the time to
On Mon, Apr 29, 2013 at 1:04 PM, Benjamin Root ben.r...@ou.edu wrote:
On Thu, Apr 25, 2013 at 11:16 AM, Charles R Harris
charlesr.har...@gmail.com wrote:
Hi All,
I think it is time to start the runup to the 1.8 release. I don't know of
any outstanding blockers but if anyone has a
On Mon, Apr 29, 2013 at 12:07 PM, Charles R Harris
charlesr.har...@gmail.com wrote:
It would be good to get the utc-everywhere fix for datetime64 in there if
someone has time to look into it.
+1
I've been on vacation, so haven't written up the various notes and
comments as a NEP yet --
On Mon, Apr 29, 2013 at 12:12 PM, Chris Barker - NOAA Federal
chris.bar...@noaa.gov wrote:
It would be good to get the utc-everywhere fix for datetime64 in there if
someone has time to look into it.
I'll see if I can open an issue for the easy fix.
DONE: Issue #3290
--
Christopher
Hi All,
I think it is time to start the runup to the 1.8 release. I don't know of
any outstanding blockers but if anyone has a PR/issue that they feel needs
to be in the next Numpy release now is the time to make it known.
Chuck
___
NumPy-Discussion
Charles R Harris charlesr.harris at gmail.com writes:
Hi All,I think it is time to start the runup to the 1.8 release. I don't
know of any outstanding blockers but if anyone has a PR/issue that they feel
needs to be in the next Numpy release now is the time to make it known.Chuck
It would
On Thu, 2013-04-25 at 09:16 -0600, Charles R Harris wrote:
Hi All,
I think it is time to start the runup to the 1.8 release. I don't know
of any outstanding blockers but if anyone has a PR/issue that they
feel needs to be in the next Numpy release now is the time to make it
known.
Sounds
I would love to get the following pull requests of mine merged in:
https://github.com/numpy/numpy/pull/2822
https://github.com/numpy/numpy/pull/462
https://github.com/numpy/numpy/pull/359
https://github.com/numpy/numpy/pull/2821
The last one probably requires a bit more work, but I'm still
Hi,
On Mon, Jan 14, 2013 at 12:19 AM, David Cournapeau courn...@gmail.com wrote:
On Sun, Jan 13, 2013 at 5:26 PM, Nathaniel Smith n...@pobox.com wrote:
On Sun, Jan 13, 2013 at 7:03 PM, Charles R Harris
charlesr.har...@gmail.com wrote:
Now that 1.7 is nearing release, it's time to look forward
Hi,
I don't volontear for the next release manager, but +1 for shorter
releases. I heard just good comments from that. Also, I'm not sure it
would ask more from the release manager. Do someone have an idea? The
most work I do as a release manager for theano is the
preparation/tests/release notes
On Mon, Jan 14, 2013 at 1:19 AM, David Cournapeau courn...@gmail.comwrote:
On Sun, Jan 13, 2013 at 5:26 PM, Nathaniel Smith n...@pobox.com wrote:
On Sun, Jan 13, 2013 at 7:03 PM, Charles R Harris
charlesr.har...@gmail.com wrote:
Now that 1.7 is nearing release, it's time to look forward to
On Mon, Jan 14, 2013 at 4:45 PM, Frédéric Bastien no...@nouiz.org wrote:
I don't volontear for the next release manager, but +1 for shorter
releases. I heard just good comments from that. Also, I'm not sure it
would ask more from the release manager. Do someone have an idea? The
most work I do
Now that 1.7 is nearing release, it's time to look forward to the 1.8
release. I'd like us to get back to the twice yearly schedule that we tried
to maintain through the 1.3 - 1.6 releases, so I propose a June release as
a goal. Call it the Spring Cleaning release. As to content, I'd like to see
On Sun, Jan 13, 2013 at 7:03 PM, Charles R Harris
charlesr.har...@gmail.com wrote:
Now that 1.7 is nearing release, it's time to look forward to the 1.8
release. I'd like us to get back to the twice yearly schedule that we tried
to maintain through the 1.3 - 1.6 releases, so I propose a June
On Sun, Jan 13, 2013 at 4:26 PM, Nathaniel Smith n...@pobox.com wrote:
On Sun, Jan 13, 2013 at 7:03 PM, Charles R Harris
charlesr.har...@gmail.com wrote:
Now that 1.7 is nearing release, it's time to look forward to the 1.8
release. I'd like us to get back to the twice yearly schedule that
On Sun, Jan 13, 2013 at 5:26 PM, Nathaniel Smith n...@pobox.com wrote:
On Sun, Jan 13, 2013 at 7:03 PM, Charles R Harris
charlesr.har...@gmail.com wrote:
Now that 1.7 is nearing release, it's time to look forward to the 1.8
release. I'd like us to get back to the twice yearly schedule that we
19 matches
Mail list logo
