Preparing release 0.3

astropy · Jun 28, 2016 · 19e4538 · 19e4538
1 parent 8f52466
commit 19e4538
Show file tree

Hide file tree

Showing 3 changed files with 4 additions and 4 deletions.
diff --git a/CHANGES.rst b/CHANGES.rst
@@ -1,4 +1,4 @@
-0.3 (unreleased)
+0.3 (2016-06-28)
 ----------------
 
 - Removed distant_observer_redshift function from mock_survey module

diff --git a/README.md b/README.md
@@ -102,7 +102,7 @@ Although the *sim_manager* provides an object-oriented framework for creating a
 
 [![Coverage Status](https://coveralls.io/repos/astropy/halotools/badge.svg?branch=master&service=github)](https://coveralls.io/github/astropy/halotools?branch=master)
 
-Halotools is a fully open-source package with contributing scientists spread across many universities. The first stable release of the package, v0.2, is now available on pip. Halotools is and will remain an evolving software package, but the API of the classes, methods and functions in v0.2 is stable. 
+Halotools is a fully open-source package with contributing scientists spread across many universities. The latest stable release of the package, v0.3, is now available on pip. You can also install the development version of the package by cloning the master branch on GitHub and locally building the source code, as described in the installation instructions. 
 
 ---
 
@@ -118,7 +118,7 @@ The google group also serves as a public forum for asking questions about the co
 
 ## Citing Halotools
 
-The v0.2 release is accompanied with a code-release paper, http://arxiv.org/abs/1606.04106. If you use Halotools modules to support your science publication, we ask that you cite this paper in your work. See the *License and Citation Information* section of http://halotools.readthedocs.io for further information about how to properly cite Halotools and its supporting science and software. 
+If you use Halotools modules to support your science publication, we ask that you cite the code-release paper, http://arxiv.org/abs/1606.04106 paper. Depending on what modules you use, other citations may also be appropriate; see the *License and Citation Information* section of http://halotools.readthedocs.io for further information about how to properly cite Halotools and its supporting science and software. 
 
 
 ---

diff --git a/setup.py b/setup.py
@@ -52,7 +52,7 @@
 builtins._ASTROPY_PACKAGE_NAME_ = PACKAGENAME
 
 # VERSION should be PEP386 compatible (http://www.python.org/dev/peps/pep-0386)
-VERSION = '0.3.dev'
+VERSION = '0.3'
 
 # Indicates if this version is a release version
 RELEASE = 'dev' not in VERSION