Hi All, There is a PR for the updated NumPy 1.15.0 release notes <https://github.com/numpy/numpy/pull/11327> . I would appreciate it if all those involved in the thatn release would have a look and fix incorrect or missing notes. Cheers, Chuck
Hi Chuck, Are you planning on doing an rc release this time? I think the NumPy 1.14 release was unusually bumpy and part of that was the lack of an rc. One example: importing h5py caused a warning under numpy 1.14 and an h5py release didn’t come out with a workaround or fix for a couple months. There was also an issue with array printing that caused problems in yt (although both yt and NumPy quickly did bugfix releases that fixed that). I guess 1.14 was particularly noisy, but still I’d really appreciate having a prerelease version to test against and some time to report issues with the prerelease so numpy and other projects can implement workarounds as needed without doing a release that might potentially break real users who happen to install right after numpy 1.x.0 comes out. Best, Nathan Goldbaum On Wed, Jun 13, 2018 at 7:11 PM Charles R Harris <charlesr.harris@gmail.com> wrote:
Request for a -rc seconded (although this time we should be fine for astropy, as things are working well with -dev). -- Marten
On Wed, Jun 13, 2018 at 6:28 PM, Nathan Goldbaum <nathan12343@gmail.com> wrote:
There was a 1.14.0rc1 <https://github.com/numpy/numpy/releases/tag/v1.14.0rc1>. I was too quick for the full release, just waited three weeks, so maybe four this time. Too few people actually test the candidates and give feedback, so I tend to regard the *.*.0 releases as the true rc :) Chuck
Hi Nathan, One very helpful think you could do, is add a Travis-CI matrix entry where you are testing against the latest numpy nightly builds. I got a bit lost in your tox setup, but the basic idea is that, for one test entry, you add the following flags to pip: -f https://7933911d6844c6c53a7d-47bd50c35cd79bd838daf386af554a83.ssl.cf2.rackcd... --pre In that case, you'll pull in the latest nightly build of Numpy. See the Scipy .travis.yml setup for an example. Cheers, Matthew On Thu, Jun 14, 2018 at 2:16 AM, Nathan Goldbaum <nathan12343@gmail.com> wrote:
Indeed, we do something similar in astropy, with a pre-release failure being considered breakage (rather than ignorable as for -dev): https://github.com/astropy/astropy/blob/master/.travis.yml#L142 -- Marten
Hi Chuck, Are you planning on doing an rc release this time? I think the NumPy 1.14 release was unusually bumpy and part of that was the lack of an rc. One example: importing h5py caused a warning under numpy 1.14 and an h5py release didn’t come out with a workaround or fix for a couple months. There was also an issue with array printing that caused problems in yt (although both yt and NumPy quickly did bugfix releases that fixed that). I guess 1.14 was particularly noisy, but still I’d really appreciate having a prerelease version to test against and some time to report issues with the prerelease so numpy and other projects can implement workarounds as needed without doing a release that might potentially break real users who happen to install right after numpy 1.x.0 comes out. Best, Nathan Goldbaum On Wed, Jun 13, 2018 at 7:11 PM Charles R Harris <charlesr.harris@gmail.com> wrote:
Request for a -rc seconded (although this time we should be fine for astropy, as things are working well with -dev). -- Marten
On Wed, Jun 13, 2018 at 6:28 PM, Nathan Goldbaum <nathan12343@gmail.com> wrote:
There was a 1.14.0rc1 <https://github.com/numpy/numpy/releases/tag/v1.14.0rc1>. I was too quick for the full release, just waited three weeks, so maybe four this time. Too few people actually test the candidates and give feedback, so I tend to regard the *.*.0 releases as the true rc :) Chuck
Hi Nathan, One very helpful think you could do, is add a Travis-CI matrix entry where you are testing against the latest numpy nightly builds. I got a bit lost in your tox setup, but the basic idea is that, for one test entry, you add the following flags to pip: -f https://7933911d6844c6c53a7d-47bd50c35cd79bd838daf386af554a83.ssl.cf2.rackcd... --pre In that case, you'll pull in the latest nightly build of Numpy. See the Scipy .travis.yml setup for an example. Cheers, Matthew On Thu, Jun 14, 2018 at 2:16 AM, Nathan Goldbaum <nathan12343@gmail.com> wrote:
Indeed, we do something similar in astropy, with a pre-release failure being considered breakage (rather than ignorable as for -dev): https://github.com/astropy/astropy/blob/master/.travis.yml#L142 -- Marten
participants (4)
-
Charles R Harris -
Marten van Kerkwijk -
Matthew Brett -
Nathan Goldbaum