[Numpy-svn] [numpy/numpy] d195f4: REL: update Paver file to ensure sdist contents ar...
GitHub
noreply at github.com
Fri Oct 16 12:02:54 EDT 2015
Branch: refs/heads/maintenance/1.10.x
Home: https://github.com/numpy/numpy
Commit: d195f4d7f5921fe8512d8cd45f2052a2ed0409be
https://github.com/numpy/numpy/commit/d195f4d7f5921fe8512d8cd45f2052a2ed0409be
Author: Ralf Gommers <ralf.gommers at gmail.com>
Date: 2015-10-16 (Fri, 16 Oct 2015)
Changed paths:
M pavement.py
Log Message:
-----------
REL: update Paver file to ensure sdist contents are OK for releases.
Commit: 54363d6e79688420c679d356ddcd2c7c73e4ba6e
https://github.com/numpy/numpy/commit/54363d6e79688420c679d356ddcd2c7c73e4ba6e
Author: Ralf Gommers <ralf.gommers at gmail.com>
Date: 2015-10-16 (Fri, 16 Oct 2015)
Changed paths:
R release.sh
Log Message:
-----------
REL: remove release.sh because it's not in use anymore.
We're using numpy-vendor/fabfile.py instead.
Commit: c0495e7052900e9321ab009e45d9cd2b83f8a043
https://github.com/numpy/numpy/commit/c0495e7052900e9321ab009e45d9cd2b83f8a043
Author: Ralf Gommers <ralf.gommers at gmail.com>
Date: 2015-10-16 (Fri, 16 Oct 2015)
Changed paths:
M doc/HOWTO_RELEASE.rst.txt
M numpy/testing/nosetester.py
Log Message:
-----------
TST: raise errors for dev versions and warnings for releases on test runs.
This approach is less error prone than switching from "develop" to "release"
in maintenance branches by hand. See gh-6461 for details.
Commit: 0b27f9c6a875ade191e9bbcd5ca1148969c6edff
https://github.com/numpy/numpy/commit/0b27f9c6a875ade191e9bbcd5ca1148969c6edff
Author: Charles Harris <charlesr.harris at gmail.com>
Date: 2015-10-16 (Fri, 16 Oct 2015)
Changed paths:
M doc/HOWTO_RELEASE.rst.txt
M numpy/testing/nosetester.py
M pavement.py
R release.sh
Log Message:
-----------
Merge pull request #6483 from charris/backport-6474
Backport 6474
Compare: https://github.com/numpy/numpy/compare/f0b4d2111d8e...0b27f9c6a875
More information about the Numpy-svn
mailing list