Remove typewriter style returns. Slight wording changes. Update manifests.

8 files changed, 746 insertions, 544 deletions

diff --git a/source/contributing.rst b/source/contributing.rst
index 7e3affd..efe157b 100644
--- a/source/contributing.rst
+++ b/source/contributing.rst
@@ -26,11 +26,10 @@ Guidelines
 Adding a recipe to astroconda-contrib
 =====================================
 
-In this example we will be adding a new recipe to the AstroConda repository for `sympy <http://sympy.org>`_, the symbolic
-mathematics library.
+In this example we will be adding a new recipe to the AstroConda repository for `sympy <http://sympy.org>`_, the
+symbolic mathematics library.
 
-Navigate to the `astroconda-contrib <https://github.com/astroconda/astroconda-contrib>`_ repository on GitHub, login,
-and create a fork (or click `here <https://github.com/astroconda/astroconda-contrib/fork>`_ to have your fork created automatically).
+Navigate to the `astroconda-contrib <https://github.com/astroconda/astroconda-contrib>`_ repository on GitHub, login, and create a fork (or click `here <https://github.com/astroconda/astroconda-contrib/fork>`_ to have your fork created automatically).
 
 Now that you have a fork of astroconda-contrib, go ahead and clone it to your system:
 
@@ -53,9 +52,8 @@ Git will automatically switch your branch from ``master`` to ``sympy-contrib`` a
     Branch sympy-contrib set up to track local branch master.
     Switched to a new branch 'sympy-contrib'
 
-If you have taken the liberty of looking around the astroconda-contrib directory, you will have noticed a bunch of
-directories are sitting in there all named by-package. So let's keep things simple and straight forward. Go ahead and
-create a directory and name it ``sympy``, and proceed inside:
+If you have taken the liberty of looking around the astroconda-contrib directory, you will have noticed a bunch of directories are sitting in there all named by-package. So let's keep things simple and straight forward. Go ahead and create a directory and name it
+``sympy``, and proceed inside:
 
 .. code-block:: sh
 
@@ -64,14 +62,11 @@ create a directory and name it ``sympy``, and proceed inside:
 
 .. note::
 
-    This is not an Anaconda packaging tutorial. For more information about creating recipes from scratch, please refer to
-    the `conda-build documentation <http://conda.pydata.org/docs/build_tutorials/pkgs2.html>`_.
+    This is not an Anaconda packaging tutorial. For more information about creating recipes from scratch, please refer to the `conda-build documentation <http://conda.pydata.org/docs/build_tutorials/pkgs2.html>`_.
 
-    **Hint:** Investigate the contents of the recipes in astroconda-contrib. For most cases, copying an existing recipe and
-    changing its values will suffice.
+    **Hint:** Investigate the contents of the recipes in astroconda-contrib. For most cases, copying an existing recipe and changing its values will suffice.
 
-Copy the contents of the ``astroconda-contrib/template`` recipe.  Three files ``bld.bat``, ``build.sh``, and ``meta.yaml``
-will be copied to your working directory:
+Copy the contents of the ``astroconda-contrib/template`` recipe.  Three files ``bld.bat``, ``build.sh``, and ``meta.yaml`` will be copied to your working directory:
 
 .. code-block:: sh
 
@@ -82,13 +77,14 @@ Go ahead and open ``meta.yaml`` with your favorite plain-text editor:
 
 .. caution::
 
-    It is *highly recommended* that you enable "tabs to spaces" for your editor. Tab widths are unpredictable and may cause
-    Conda's YAML parser to fail.
+    It is *highly recommended* that you enable "tabs to spaces" for your editor. Tab widths are unpredictable and may
+     cause Conda's YAML parser to fail.
 
 .. code-block:: sh
 
     vim meta.yaml
 
+
 The general structure of the file is as follows:
 
 .. code-block:: yaml
@@ -146,6 +142,7 @@ First, let's fill in the blanks. Modify the JINJA2 template markers for ``name``
     {% set name = 'sympy' %}
     {% set version = '1.0' %}
 
+
 Fill in the ``about`` section with relevant information regarding the package:
 
 .. code-block:: yaml
@@ -155,6 +152,7 @@ Fill in the ``about`` section with relevant information regarding the package:
         license: GPL
         summary: Python library for symbolic mathematics
 
+
 Next, modify the ``source`` section's ``url`` so that it points to ``sympy``'s source archive (on the internet):
 
 .. code-block:: sh
@@ -163,21 +161,14 @@ Next, modify the ``source`` section's ``url`` so that it points to ``sympy``'s s
         fn: {{ name }}-{{ version }}.tar.gz
         url: https://github.com/{{ name }}/{{ name }}/releases/download/{{ name }}-{{ version }}/{{ name }}-{{ version }}.tar.gz
 
-What's with the never-ending stream of bracket encapsulated keywords, you ask? Conda uses JINJA2, a basic template system that
-provides basic string interpolation within recipes. This comes in handy if, let's say, you decide to build a more recent version of ``sympy``,
-you need only modify the first two variable definitions in this file (assuming the URL structure has not changed).
 
-The ``requirements`` section may be confusing to some, so let's clarify the distinction between ``build`` and ``run`` before diving in.
-The ``build`` section defines Conda packages required at compile-time (i.e. ``python setup.py install``), whereas the ``run`` section
-lists Conda packages required at install-time (i.e. ``conda install [package]``).
+What's with the never-ending stream of bracket encapsulated keywords, you ask? Conda uses JINJA2, a basic template system that provides basic string interpolation within recipes. This comes in handy if, let's say, you decide to build a more recent version of ``sympy``, you need only modify the first two variable definitions in this file (assuming the URL structure has not changed).
+
+The ``requirements`` section may be confusing to some, so let's clarify the distinction between ``build`` and ``run`` before diving in. The ``build`` section defines Conda packages required at compile-time (i.e. ``python setup.py install``), whereas the ``run`` section lists Conda packages required at install-time (i.e. ``conda install [package]``).
 
-As recipe maintainer the method used to dependency discover is that of trial and error. For many Python packages obtained via
-PyPi, it is easy enough to visually examine ``setup.py`` or ``requirements.txt`` to get a good idea of the recipes you need to
-depend on. Some package may require several iterations of executing ``conda-build`` and returning to your recipe in the editor
-to append more packages.
+As recipe maintainer the method used to dependency discover is that of trial and error. For many Python packages obtained via PyPi, it is easy enough to visually examine ``setup.py`` or ``requirements.txt`` to get a good idea of the recipes you need to depend on. Some package may require several iterations of executing ``conda-build`` and returning to your recipe in the editor to append more packages.
 
-As we can see below, ``sympy`` requires ``mpmath``, ``setuptools`` and ``python`` to *build* the recipe, but only
-``mpmath`` and ``python`` to *run it* successfully after installation:
+As we can see below, ``sympy`` requires ``mpmath``, ``setuptools`` and ``python`` to *build* the recipe, but only ``mpmath`` and ``python`` to *run it* successfully after installation:
 
 .. code-block:: yaml
 
@@ -190,14 +181,10 @@ As we can see below, ``sympy`` requires ``mpmath``, ``setuptools`` and ``python`
         - mpmath
         - python x.x
 
-What does the ``x.x`` imply exactly? This instructs ``conda-build`` *not* to proceed unless ``python=[version]`` has
-been issued as an argument on the commandline. If ``x.x`` is omitted here, the recipe will choose the version of Python
-currently active in your environment. In most cases it is best to be explicit rather than implicit when it comes to defining
-version requirements in Conda.
+What does the ``x.x`` imply exactly? This instructs ``conda-build`` *not* to proceed unless ``python=[version]`` has been issued as an argument on the commandline. If ``x.x`` is omitted here, the recipe will choose the version of Python currently active in your environment. In most cases it is best to be explicit rather than implicit when it comes to defining version requirements in Conda.
 
-The ``test`` section defines few useful lists, ``imports``, ``commands``, and ``requires``. While these are not *required* to be used in any given recipe,
-we do use them in AstroConda. The ``imports`` section is a list of Python module imports, the ``commands`` are executed in a
-basic shell environment, and finally ``requires`` defines any extraneous packages to be installed into the environment before running the tests.
+The ``test`` section defines few useful lists, ``imports``, ``commands``, and ``requires``. While these are not *required* to be used in any given recipe, we do use them in AstroConda. The ``imports`` section is a list of Python module imports, the ``commands``
+are executed in a basic shell environment, and finally ``requires`` defines any extraneous packages to be installed into the environment before running the tests.
 
 .. code-block:: yaml
 
@@ -211,8 +198,7 @@ basic shell environment, and finally ``requires`` defines any extraneous package
         #requires:
         #   - does not require any extra testing-related packages
 
-If ``sympy`` provided a commandline utility named ``sympy-show``, you would use the ``commands`` section to verify
-the utility's functionality. A simple example of this would be to output a usage statement.
+If ``sympy`` provided a commandline utility named ``sympy-show``, you would use the ``commands`` section to verify the utility's functionality. A simple example of this would be to output a usage statement.
 
 .. code-block:: sh
 
@@ -221,12 +207,10 @@ the utility's functionality. A simple example of this would be to output a usage
         commands:
             - sympy-show --help
 
-If a program returns greater than zero ``conda-build`` will fail as if it observed an error. Not all programs return zero after issuing
-``--help`` (or an equivalent argument). Due to this, you may need to omit this style of test.
+If a program returns greater than zero ``conda-build`` will fail as if it observed an error. Not all programs return zero after issuing ``--help`` (or an equivalent argument). Due to this, you may need to omit this style of test.
 
-It will not hurt to keep the ``commands`` section
-populated but disabled with a note describing why it doesn't work. Others will find this information useful. Given this scenario, the
-optimal approach would be to contact the developers and plead with them to normalize the exit value.
+It will not hurt to keep the ``commands`` section populated but disabled with a note describing why it doesn't work. Others will find this information useful. Given this scenario, the optimal approach would be to contact the developers and plead with them to
+normalize the exit value.
 
 
 Below is our ``sympy`` final recipe. Despite the overwhelming use of JINGA2 in our example, things are looking pretty streamlined.
@@ -259,13 +243,9 @@ Below is our ``sympy`` final recipe. Despite the overwhelming use of JINGA2 in o
             - sympy
 
 
-The ``template`` directory copied earlier in this tutorial contains two basic python build scripts for both \*Nix (``build.sh``) and Windows (``bld.bat``),
-and is coincidentally compatible with the example we're using here. Not all Python packages (especially Makefile-based packages) will compile successfully
-using this "one-liner" template. Always refer to the ``INSTALL`` file or equivalent documentation for the program you are attempting to compile to learn
-more about what the package expects from the end-user at compile-time.
+The ``template`` directory copied earlier in this tutorial contains two basic python build scripts for both \*Nix (``build.sh``) and Windows (``bld.bat``), and is coincidentally compatible with the example we're using here. Not all Python packages (especially Makefile-based packages) will compile successfully using this "one-liner" template. Always refer to the ``INSTALL`` file or equivalent documentation for the program you are attempting to compile to learn more about what the package expects from the end-user at compile-time.
 
-Before we can issue a pull request on GitHub, we first ensure it builds, tests, and installs properly on our local system.
-To do this we need to change our directory to one level above the recipe.
+Before we can issue a pull request on GitHub, we first ensure it builds, tests, and installs properly on our local system. To do this we need to change our directory to one level above the recipe.
 
 .. code-block:: sh
 
@@ -279,14 +259,9 @@ Python 3.5:
 
     conda-build -c http://ssb.stsci.edu/astroconda --skip-existing --python=3.5 sympy
 
-That's probably a bit more involved than you thought. Let's break it down. We issue ``-c [URL]`` which instructs the build to utilize
-the AstroConda channel while checking for package dependencies (i.e. the recipe's ``requirements`` section). Secondly, we issue
-``--skip-existing`` to prevent ``conda-build`` from rebuilding dependencies discovered in the local astroconda-contrib directory.
-That is to say, if a package defined as a requirement exists remotely, it will then download and install it, rather than rebuild it from scratch.
-``--python=`` is self-explanatory, and the final argument is the name of the recipe(s) we intend to build.
+That's probably a bit more involved than you thought. Let's break it down. We issue ``-c [URL]`` which instructs the build to utilize the AstroConda channel while checking for package dependencies (i.e. the recipe's ``requirements`` section). Secondly, we issue ``--skip-existing`` to prevent ``conda-build`` from rebuilding dependencies discovered in the local astroconda-contrib directory. That is to say, if a package defined as a requirement exists remotely, it will then download and install it, rather than rebuild it from scratch. ``--python=`` is self-explanatory, and the final argument is the name of the recipe(s) we intend to build.
 
-At this point, if the build was successful, our Conda package (a bzipped tarball) called ``sympy-1.0-py35_0.tar.bz2`` is emitted to ``/path/to/anaconda/conda-bld/[os-arch]/``.
-This directory is a local Conda package repository.
+At this point, if the build was successful, our Conda package (a bzipped tarball) called ``sympy-1.0-py35_0.tar.bz2`` is emitted to ``/path/to/anaconda/conda-bld/[os-arch]/``. This directory is a local Conda package repository.
 
 To install this new ``sympy`` package and interact with it ourselves you could run the following:
 
@@ -309,8 +284,7 @@ And checking it out for yourself:
     >>> sympy.__file__
     '/path/to/anaconda/envs/sympy_test/lib/python3.5/site-packages/sympy/__init__.py'
 
-Now that you have verified the recipe is fully functional and are happy with the outcome, it's time to create a pull request
-against astroconda-contrib main repository.
+Now that you have verified the recipe is fully functional and are happy with the outcome, it's time to create a pull request against astroconda-contrib main repository.
 
 Push your ``sympy-contrib`` branch up to your fork on GitHub:
 
@@ -321,11 +295,9 @@ Push your ``sympy-contrib`` branch up to your fork on GitHub:
 
 It is recommended that you familiarize yourself with GitHub pull requests before proceeding (see: `tutorial <https://help.github.com/articles/using-pull-requests/>`_).
 
-Using GitHub, you will want to browse to your ``astroconda-contrib`` fork, select the ``sympy-contrib`` branch from the drop-down menu
-(the default will read: "Branch: master", next to a black downward-pointing caret). Once selected, click the large green button labeled: "New pull request".
+Using GitHub, you will want to browse to your ``astroconda-contrib`` fork, select the ``sympy-contrib`` branch from
+the drop-down menu (the default will read: "Branch: master", next to a black downward-pointing caret). Once selected, click the large green button labeled: "New pull request".
 
-From here, you may wish to edit the title of your pull request and add initial comments or notes regarding what you have done, or
-list any work that may still need to be done. After submitting your pull request, a member of the Science Software Branch at STScI, or fellow contributors
-will review the requested changes, ask questions, offer feedback or advice.
+From here, you may wish to edit the title of your pull request and add initial comments or notes regarding what you have done, or list any work that may still need to be done. After submitting your pull request, a member of the Science Software Branch at STScI, or fellow contributors will review the requested changes, ask questions, offer feedback or advice.
 
 At this point if everything appears to be in order your recipe will likely be merged, built, and incorporated into AstroConda!
diff --git a/source/faq.rst b/source/faq.rst
index c516df2..4a8a43c 100644
--- a/source/faq.rst
+++ b/source/faq.rst
@@ -3,30 +3,27 @@ F.A.Q.
 ######
 
 
-After "``conda create ...``" why does "``source activate astroconda``" fail?
+After "conda create -n ..." why does "source activate astroconda" fail?
 ============================================================================
 
 Anaconda does not support CSH (C-Shell). Please switch to a POSIX-compatible shell (e.g. BASH, KSH, ZSH).
 
 .. note::
 
-    STScI will not maintain a separate codebase of Anaconda's backend ``conda`` in order to implement CSH support. Feel free to
-    create an issue with the `developers <http://github.com/conda/conda/issues>`_.
+    STScI will not maintain a separate codebase of Anaconda's backend ``conda`` in order to implement CSH support. Feel free to create an issue with the `developers <http://github.com/conda/conda/issues>`_.
 
 I installed AstroConda into my Anaconda 'root' environment. What now?
 =====================================================================
 
-Please reinstall Anaconda from scratch. AstroConda uses ``source activate`` and ``source deactivate`` calls to control your shell
-environment. The Anaconda 'root' environment **does not** use this feature, and thus, the packages you have installed there will not work properly.
-To clarify, it is impossible to execute ``source activate root``. Installing AstroConda packages directly into the 'root' may cause
-Anaconda itself to be come unstable. In addition to this, removing packages from this environment is tedious and will likely break
-your Anaconda installation if you are not careful. *Reinstalling from scratch is the safest option.*
+Please reinstall Anaconda from scratch. AstroConda uses ``source activate`` and ``source deactivate`` calls to
+control your shell environment. The Anaconda 'root' environment **does not** use this feature, and thus, the packages you have installed there will not work properly.
+
+To clarify, it is impossible to execute ``source activate root``. Installing AstroConda packages directly into the 'root' may cause Anaconda itself to be come unstable. In addition to this, removing packages from this environment is tedious and will likely break your Anaconda installation if you are not careful. *Reinstalling from scratch is the safest option.*
 
 Why am I being prompted by NumPy/SciPy with a MKL 30-day trial warning?
 =======================================================================
 
-The ``root`` environment of your Anaconda installation is severely outdated (``<=2.4.0``) and suffers from a crippling bug
-introduced by the ``conda-3.19.x`` package.
+The ``root`` environment of your Anaconda installation is severely outdated (``<=2.4.0``) and suffers from a crippling bug introduced by the ``conda-3.19.x`` package.
 
 It is possible to verify the version of Anaconda you have by running:
 
@@ -50,47 +47,34 @@ Next, update the ``astroconda`` environment to realign your packages with the ``
     $ source activate astroconda
 
 After doing this, the ``mkl`` 30-day trial warning will not be displayed while importing ``numpy``, ``scipy``, or any
-other package requiring ``mkl``.
+ other package requiring ``mkl``.
 
 How does AstroConda differ from Ureka?
 ======================================
 
-Ureka and AstroConda both provide applications and libraries in binary form, however Ureka was a *one size fits all* distribution
-which included every package in one giant tarball. If an end-user only really wanted a small set of packages they were forced
-to install everything *and then some*. AstroConda is a *if the shoe fits wear it* distribution of packages. If an end-user
-needs ``HSTCAL``, for example, they can install ``HSTCAL`` and omit much of the rest of HST's software suite.
+Ureka and AstroConda both provide applications and libraries in binary form, however Ureka was a *one size fits all* distribution which included every package in one giant tarball. If an end-user only really wanted a small set of packages they were forced to install everything *and then some*. AstroConda is a *if the shoe fits wear it* distribution of packages. If an end-user needs ``HSTCAL``, for example, they can install ``HSTCAL`` and omit much of the rest of HST's software suite.
 
-A *major difference* most people will appreciate is the sheer lack of shell scripts. Ureka's environment was controlled by
-several dozen independent scripts. What makes AstroConda different? For one, it is not controlled by user-executed scripts.
-Changes to the environment are applied by special (read: embedded) scripts that are executed automatically by ``source activate``,
-and the environment variables are unset with every ``source deactivate``. This allows you to switch between several different
-environments rapidly without needing to keep track of what is defined in the environment.
+A *major difference* most people will appreciate is the sheer lack of shell scripts. Ureka's environment was controlled by several dozen independent scripts. What makes AstroConda different? For one, it is not controlled by user-executed scripts. Changes to the environment are applied by special (read: embedded) scripts that are executed automatically by ``source activate``, and the environment variables are unset with every ``source deactivate``. This allows you to switch between several different environments rapidly without needing to keep track of what is
+defined in the environment.
 
 How often are updates released?
 ===============================
 
-Updates to (STScI) software will be released as bugs are identified and squashed. The ``stsci-*`` metapackages, for example, provide
-"releases" (i.e. a set of software used by our internal pipelines). After installing a release it is then possible to upgrade to the latest
-out-of-band packages by simply running:
+Updates to (STScI) software will be released as bugs are identified and squashed. The ``stsci-*`` metapackages, for example, provide "releases" (i.e. a set of software used by our internal pipelines). After installing a release it is then possible to upgrade to the latest out-of-band packages by simply running:
 
 ``conda update -n astroconda --all``
 
-Non-STScI software will be upgraded on an as-needed basis. See the `Contibuting Guide <contributing.html>`_ to learn more about asking
-for updates to existing packages.
+Non-STScI software will be upgraded on an as-needed basis. See the `Contibuting Guide <contributing.html>`_ to learn more about asking for updates to existing packages.
 
 What happened to SSBX?
 ======================
 
-SSBX was a weekly release of STScI's software suite regardless of the stability of the codebase. This release was often times
-broken and caused issues for external users. SSBX has been rolled into AstroConda as out-of-band package updates. This offers
-a much better user experience, because as bugs are fixed, people will be able to upgrade without waiting until the following week.
+SSBX was a weekly release of STScI's software suite regardless of the stability of the codebase. This release was often times broken and caused issues for external users. SSBX has been rolled into AstroConda as out-of-band package updates. This offers a much better user experience, because as bugs are fixed, people will be able to upgrade without waiting until the following week.
 
 What happened to SSBDEV?
 ========================
 
-SSBDEV was a nightly snapshot release of STScI's software suite. This release was often times broken and caused issues for
-external users. Nightly snapshots are ***no longer available*** for use by the public. Updates to AstroConda will be made
-directly as existing software is improved and/or new software is released.
+SSBDEV was a nightly snapshot release of STScI's software suite. This release was often times broken and caused issues for external users. Nightly snapshots are ***no longer available*** for use by the public. Updates to AstroConda will be made directly as existing software is improved and/or new software is released.
 
 Why isn't IRAF installed by default?
 ====================================
@@ -110,18 +94,15 @@ If you are already using AstroConda under a Python 2 environment, you may simply
 Why is IRAF/PyRAF less functional under Python 3?
 =================================================
 
-The Python code in ``stsdas``, for example, is targeted specifically for Python 2.7 and earlier. If the demand for Python 3
-support under IRAF is great enough we may be able to pull our resources to accommodate the community. It is recommended to install
-IRAF into its own environment under Python 2.7:
+The Python code in ``stsdas``, for example, is targeted specifically for Python 2.7 and earlier. If the demand for Python 3 support under IRAF is great enough we may be able to pull our resources to accommodate the community. It is recommended to install IRAF into its
+ own environment under Python 2.7:
 
 ``conda create -n iraf27 python=2.7 iraf pyraf stsci && source activate iraf27``
 
 Why is IRAF 32-bit instead of 64-bit?
 =====================================
 
-Many of the IRAF tasks that we include with AstroConda are so old that they cannot be compiled as 64-bit executables
-without significant changes to the source code. Because of this restriction, we always build IRAF as a 32-bit program, even
-for our 64-bit distributions.
+Many of the IRAF tasks that we include with AstroConda are so old that they cannot be compiled as 64-bit executables without significant changes to the source code. Because of this restriction, we always build IRAF as a 32-bit program, even for our 64-bit distributions.
 
 In Linux, how do I install IRAF's 32-bit dependencies?
 ------------------------------------------------------
@@ -147,7 +128,6 @@ RHEL/CentOS >=6, Fedora >=14
 Will AstroConda interfere with other scientific distributions (e.g. SciSoft)?
 =============================================================================
 
-**Probably**, however unlike Ureka, we do not impose any restrictions on your environment or issue compatibility warnings at run-time.
-It is your responsibility to maintain a functional shell environment so [insert scientific distribution here] does not conflict with your Anaconda
-installation.
+**Probably**, however unlike Ureka, we do not impose any restrictions on your environment or issue compatibility
+warnings at run-time. It is your responsibility to maintain a functional shell environment so [insert scientific distribution here] does not conflict with your Anaconda installation.
 
diff --git a/source/index.rst b/source/index.rst
index 5a36e9b..edfca3b 100644
--- a/source/index.rst
+++ b/source/index.rst
@@ -1,16 +1,14 @@
 Welcome to AstroConda's documentation!
 ======================================
 
-AstroConda is a free software repository maintained by the `Space Telescope Science Institute <http://www.stsci.edu/>`_ (STScI)
-in Baltimore, Maryland. This repository provides tools and utilities commonly used by the astronomical community.
+AstroConda is a free software repository maintained by the `Space Telescope Science Institute <http://www.stsci.edu/>`_ (STScI) in Baltimore, Maryland. This repository provides tools and utilities commonly used by the astronomical community.
 
-The components provided through the `astroconda <http://ssb.stsci.edu/astroconda>`_ channel on `ssb.stsci.edu <http://ssb.stsci.edu>`_
-include most of the tools the user needs to work with Hubble Space Telescope (HST) data and data from other telescopes in
-a single Anaconda Python environment.  Each of the components contains sets of packages which have also been built and tested
-to ensure that they work with each other in the same environment.
+The components provided through the `astroconda <http://ssb.stsci.edu/astroconda>`_ channel on `ssb.stsci.edu <http://ssb.stsci.edu>`_ include most of the tools the user needs to work with Hubble Space Telescope (HST) data and data from other telescopes in a single Anaconda Python environment.  Each of the components contains sets of packages which have also been built and tested to ensure that they work with each
+ other in the same environment.
 
 To receive AstroConda announcements, or to engage in general discussion, feel free to subscribe to our `mailing list <https://groups.google.com/forum/#!forum/astroconda>`_.
 
+
 .. toctree::
    :maxdepth: 2
    :titlesonly:
diff --git a/source/installation.rst b/source/installation.rst
index a8b0ec1..8bea513 100644
--- a/source/installation.rst
+++ b/source/installation.rst
@@ -5,7 +5,7 @@ Installation
 Before you begin, note the following requirements and limitations of AstroConda:
 
     - AstroConda supports Linux (glibc ≥ 2.12) and Mac OS X (≥ 10.7; 10.6 is NOT supported)
-    - AstroConda packages support Python versions 2.7, 3.4, or 3.5 on 64-bit platforms. (If you don't know whether you have a 32-bit or 64-bit processor, assume you have 64-bit.)
+    - AstroConda packages support Python versions 2.7 or 3.5 on 64-bit platforms. (If you don't know whether you have a 32-bit or 64-bit processor, assume you have 64-bit.)
     - If :abbr:`IRAF (Image Reduction and Analysis Facility)` is required as part of your personal workflow it is *highly recommended* you install Anaconda for Python 2.7 (see :ref:`iraf_python3`).
     - If you do not use :abbr:`IRAF (Image Reduction and Analysis Facility)`, choose the Anaconda installer with the Python version best suited for your scripting needs.
     - This documentation specifically targets Anaconda for Python 3 installations. However, the same commands should still work interchangeably between versions.
@@ -13,14 +13,13 @@ Before you begin, note the following requirements and limitations of AstroConda:
 Obtain Anaconda
 ===============
 
-Go grab a copy of the `Anaconda <https://www.continuum.io/downloads>`_ distribution from Continuum Analytics, Inc. Be sure to select the installation medium appropriate for your operating system (Linux or Mac) and architecture (64-bit).
+Go grab a copy of the `Anaconda <https://www.continuum.io/downloads>`_ distribution from Continuum Analytics, Inc. Be sure to select the installation medium appropriate for your operating system (Linux or OS X) and architecture (64-bit). The OS X GUI installer may cause side-effects, such as changing permissions of files in your home directory to ``root:wheel``, or mistakenly creating a system-wide installation in ``/anaconda`` instead of your personal home directory. To avoid this situation perform a command-line installation instead.
 
 Follow the installation instructions for your platform given on the download page. Before moving on to the next step, open a new terminal window, run the ``conda`` command, and ensure your terminal can find it.
 
 .. note::
 
-    Are you using ``bash`` as your shell? Run ``echo $SHELL`` in a terminal and make sure it says something like ``/bin/bash``.
-    If it does not, you will have to change your default shell (which is outside the scope of these instructions).
+    Are you using ``bash`` as your shell? Run ``echo $SHELL`` in a terminal and make sure it says something like ``/bin/bash``. If it does not, you will have to change your default shell (which is outside the scope of these instructions).
 
     In the meantime, you can start ``bash -l`` from within your terminal to use ``bash`` temporarily to follow these instructions.
 
@@ -28,10 +27,7 @@ Follow the installation instructions for your platform given on the download pag
 Configure Conda
 ===============
 
-In order to install packages directly from the AstroConda repository, you will need to configure Anaconda to do so.
-This will permanently add the repository to Conda's search path. Be aware that adding additional
-`anaconda.org <https://anaconda.org>`_ or direct-url repositories may affect the stability of AstroConda's run-time
-environment.
+In order to install packages directly from the AstroConda repository, you will need to configure Anaconda to do so. This will permanently add the repository to Conda's search path. Be aware that adding additional `anaconda.org <https://anaconda.org>`_ or direct-url repositories may affect the stability of AstroConda's run-time environment.
 
 .. code-block:: sh
 
@@ -45,9 +41,7 @@ Install AstroConda
 Standard installation (without IRAF)
 ------------------------------------
 
-Now that Conda is configured to pull from our repository, you may now go ahead and install the ``stsci`` metapackage.
-The example below will generate a new environment called "astroconda" (using the ``-n`` flag),
-however, this is merely a suggestion. Feel free to use a name that works best for you.
+Now that Conda is configured to pull from our repository, you may now go ahead and install the ``stsci`` metapackage. The example below will generate a new environment called "astroconda" (using the ``-n`` flag), however, this is merely a suggestion. Feel free to use a name that works best for you.
 
 .. code-block:: sh
 
@@ -69,12 +63,7 @@ This will prompt you to confirm the installation of all the STScI packages avail
 Installation with legacy IRAF support
 -------------------------------------
 
-The developers of AstroConda have limited resources to
-support :abbr:`IRAF (Image Reduction and Analysis Facility)`, but users that
-require the ability to run IRAF and PyRAF tasks may want to install it
-through AstroConda.  For help with many issues that come up during installation
-or use, visit the `PyRAF FAQ <http://www.stsci.edu/institute/software_hardware/pyraf/pyraf_faq>`_
-page.
+The developers of AstroConda have limited resources to support :abbr:`IRAF (Image Reduction and Analysis Facility)`, but users that require the ability to run IRAF and PyRAF tasks may want to install it through AstroConda. For help with many issues that come up during installation or use, visit the `PyRAF FAQ <http://www.stsci.edu/institute/software_hardware/pyraf/pyraf_faq>`_ page.
 
 IRAF is not installed by default, so the AstroConda install command is a little different.
 
@@ -90,11 +79,7 @@ Then, just as with the default installation, it is necessary to activate the env
 
 .. note::
 
-    Support for using Python 2.7 and IRAF is being gradually phased out by STScI
-    maintainers. In the transitional period, you may wish to install AstroConda
-    with the default settings but maintain a Python 2.7 + IRAF environment for
-    testing. The following commands create an ``astroconda`` environment with
-    the default settings, and an ``iraf27`` environment with IRAF.
+    Support for using Python 2.7 and IRAF is being gradually phased out by STScI maintainers. In the transitional period, you may wish to install AstroConda with the default settings but maintain a Python 2.7 + IRAF environment for testing. The following commands create an ``astroconda`` environment with the default settings, and an ``iraf27`` environment with IRAF.
 
     .. code-block:: sh
 
@@ -106,9 +91,7 @@ Then, just as with the default installation, it is necessary to activate the env
 Fine-tuning the installation
 ============================
 
-If you are short on hard drive space, have a slow internet connection, or are simply not interested in installing
-*everything but the kitchen sink*; please feel free to peruse the `manifest <http://ssb.stsci.edu/astroconda>`_ and
-install a custom mix of packages tailored to your needs.
+If you are short on hard drive space, have a slow internet connection, or are simply not interested in installing *everything but the kitchen sink*; please feel free to peruse the `manifest <http://ssb.stsci.edu/astroconda>`_ and install a custom mix of packages tailored to your needs.
 
 .. code-block:: sh
 
@@ -122,14 +105,19 @@ AstroConda provides a suite of packages that are known to work well together and
 
 Full documentation of the ``conda`` tool is available from Continuum Analytics, Inc., its creators and maintainers: http://conda.pydata.org/docs/using/index.html. However, we have provided a brief explanation of 3rd-party package installation below for quick reference.
 
-For scientific packages available through Anaconda, installation is as simple as::
+For scientific packages available through Anaconda, installation is as simple as:
+
+.. code-block:: sh
 
     $ source activate astroconda
     $ conda install nameofpkg
 
-Often, the easiest way to see if the package is available through Anaconda is to try installing it. The full list of packages is available here: http://repo.continuum.io/pkgs/.
+Often, the easiest way to see if the package is available through Anaconda is to try installing it. The full list of available packages is here: http://repo.continuum.io/pkgs/.
 
-The Python-standard tool ``pip`` is also available to install packages distributed through the Python Package Index (PyPI)::
+The Python-standard tool ``pip`` is also available to install packages distributed through the Python Package Index (PyPI):
+
+.. code-block:: sh
 
     $ source activate astroconda
     $ pip install nameofpkg
+
diff --git a/source/package_manifest.py b/source/package_manifest.py
index 47c5bef..a179888 100644
--- a/source/package_manifest.py
+++ b/source/package_manifest.py
@@ -4,9 +4,9 @@ from urllib.request import urlopen
 from pprint import pprint
 
 ARCHITECTURE = [ 'linux-64', 'osx-64']
-METAPACKAGES = [('stsci', '1.0.0'),
+METAPACKAGES = [('stsci', '1.0.1'),
                 ('stsci-data-analysis', '1.0.0'),
-                ('stsci-hst', '1.0.0'),
+                ('stsci-hst', '1.0.4'),
                 ('stsci-jwst', '1.0.0')]
 REPODATA_URL='http://ssb.stsci.edu/astroconda/{arch}/repodata.json'
 #REPODATA_URL='http://ssb.stsci.edu/conda-dev/{arch}/repodata.json'
diff --git a/source/package_manifest.rst b/source/package_manifest.rst
index c99bfd6..509201e 100644
--- a/source/package_manifest.rst
+++ b/source/package_manifest.rst
@@ -25,71 +25,33 @@ linux-64 metapackages
 ------------------------
 
 
-- **stsci-1.0.0 (np110py34_0)**
+- **stsci-1.0.1 (np111py27_0)**
 
     - astropy >=1.1       
 
-    - cfitsio ==3.370     
+    - cfitsio >=3.370     
 
-    - d2to1 ==0.2.12      
+    - d2to1 >=0.2.12      
 
-    - ds9 ==7.4           
+    - ds9 >=7.1           
 
-    - fftw ==3.3.4        
+    - fftw >=3.3.4        
 
     - htc_utils >=0.1     
 
-    - imexam ==0.5.2      
+    - imexam >=0.5.2      
 
-    - numpy 1.10*         
-
-    - photutils ==0.2.1   
-
-    - poppy ==0.4.0       
-
-    - purge_path >=0.0.1  
-
-    - pyds9 ==1.8.1       
-
-    - pyfftw ==0.9.2      
-
-    - python 3.4*         
-
-    - stsci-data-analysis 
-
-    - stsci-hst           
-
-    - webbpsf ==0.4.0     
-
-    - webbpsf-data ==0.4.0
-
-- **stsci-1.0.0 (np110py27_0)**
-
-    - astropy >=1.1       
+    - numpy 1.11*         
 
-    - cfitsio ==3.370     
+    - photutils >=0.2.1   
 
-    - d2to1 ==0.2.12      
+    - poppy >=0.4.0       
 
-    - ds9 ==7.4           
+    - purge_path >=1.0.0  
 
-    - fftw ==3.3.4        
+    - pyds9 >=1.8.1       
 
-    - htc_utils >=0.1     
-
-    - imexam ==0.5.2      
-
-    - numpy 1.10*         
-
-    - photutils ==0.2.1   
-
-    - poppy ==0.4.0       
-
-    - purge_path >=0.0.1  
-
-    - pyds9 ==1.8.1       
-
-    - pyfftw ==0.9.2      
+    - pyfftw >=0.9.2      
 
     - python 2.7*         
 
@@ -97,37 +59,37 @@ linux-64 metapackages
 
     - stsci-hst           
 
-    - webbpsf ==0.4.0     
+    - webbpsf >=0.4.0     
 
-    - webbpsf-data ==0.4.0
+    - webbpsf-data >=0.4.0
 
-- **stsci-1.0.0 (np110py35_0)**
+- **stsci-1.0.1 (np111py35_0)**
 
     - astropy >=1.1       
 
-    - cfitsio ==3.370     
+    - cfitsio >=3.370     
 
-    - d2to1 ==0.2.12      
+    - d2to1 >=0.2.12      
 
-    - ds9 ==7.4           
+    - ds9 >=7.1           
 
-    - fftw ==3.3.4        
+    - fftw >=3.3.4        
 
     - htc_utils >=0.1     
 
-    - imexam ==0.5.2      
+    - imexam >=0.5.2      
 
-    - numpy 1.10*         
+    - numpy 1.11*         
 
-    - photutils ==0.2.1   
+    - photutils >=0.2.1   
 
-    - poppy ==0.4.0       
+    - poppy >=0.4.0       
 
-    - purge_path >=0.0.1  
+    - purge_path >=1.0.0  
 
-    - pyds9 ==1.8.1       
+    - pyds9 >=1.8.1       
 
-    - pyfftw ==0.9.2      
+    - pyfftw >=0.9.2      
 
     - python 3.5*         
 
@@ -135,11 +97,11 @@ linux-64 metapackages
 
     - stsci-hst           
 
-    - webbpsf ==0.4.0     
+    - webbpsf >=0.4.0     
 
-    - webbpsf-data ==0.4.0
+    - webbpsf-data >=0.4.0
 
-- **stsci-data-analysis-1.0.0 (np110py27_0)**
+- **stsci-data-analysis-1.0.0 (np111py35_1)**
 
     - asdf ==1.0.2        
 
@@ -151,15 +113,15 @@ linux-64 metapackages
 
     - cube-tools ==0.0.0  
 
-    - numpy 1.10*         
+    - numpy 1.11*         
 
-    - python 2.7*         
+    - python 3.5*         
 
     - specview ==0.1      
 
     - stginga ==0.0.0     
 
-- **stsci-data-analysis-1.0.0 (np110py35_0)**
+- **stsci-data-analysis-1.0.0 (np110py34_0)**
 
     - asdf ==1.0.2        
 
@@ -173,241 +135,223 @@ linux-64 metapackages
 
     - numpy 1.10*         
 
-    - python 3.5*         
+    - python 3.4*         
 
     - specview ==0.1      
 
     - stginga ==0.0.0     
 
-- **stsci-data-analysis-1.0.0 (np110py34_0)**
+- **stsci-data-analysis-1.0.0 (np111py35_2)**
 
-    - asdf ==1.0.2        
+    - asdf >=1.0.2        
 
-    - astroimtools ==0.1  
+    - astroimtools >=0.1  
 
     - astropy >=1.1       
 
-    - asv ==0.1.1         
+    - asv >=0.1.1         
 
-    - cube-tools ==0.0.0  
+    - cube-tools >=0.0.0  
 
-    - numpy 1.10*         
+    - numpy 1.11*         
 
-    - python 3.4*         
+    - python 3.5*         
 
-    - specview ==0.1      
+    - specview >=0.1      
 
-    - stginga ==0.0.0     
+    - stginga >=0.1       
 
-- **stsci-hst-1.0.0 (np110py35_0)**
+- **stsci-data-analysis-1.0.0 (np111py27_2)**
 
-    - acstools ==2.0.0    
+    - asdf >=1.0.2        
 
-    - astrolib.coords ==0.39.6
+    - astroimtools >=0.1  
 
     - astropy >=1.1       
 
-    - calcos ==3.1.3      
-
-    - costools ==1.2.1    
-
-    - crds ==0.0.0        
+    - asv >=0.1.1         
 
-    - d2to1 ==0.2.12      
+    - cube-tools >=0.0.0  
 
-    - drizzlepac ==2.1.3  
+    - numpy 1.11*         
 
-    - fitsblender ==0.2.6 
-
-    - hstcal ==1.0.0      
-
-    - nictools ==1.1.3    
-
-    - numpy 1.10*         
-
-    - purge_path >=0.0.1  
+    - python 2.7*         
 
-    - pyregion ==1.1.2    
+    - specview >=0.1      
 
-    - pysynphot ==0.9.8.2 
+    - stginga >=0.1       
 
-    - python 3.5*         
+- **stsci-data-analysis-1.0.0 (np110py27_0)**
 
-    - pywcs ==1.12.1      
+    - asdf ==1.0.2        
 
-    - reftools ==1.7.1    
+    - astroimtools ==0.1  
 
-    - stistools ==1.1     
+    - astropy >=1.1       
 
-    - stsci.convolve ==2.1.3
+    - asv ==0.1.1         
 
-    - stsci.distutils ==0.3.8
+    - cube-tools ==0.0.0  
 
-    - stsci.image ==2.2.0 
+    - numpy 1.10*         
 
-    - stsci.imagemanip ==1.1.2
+    - python 2.7*         
 
-    - stsci.imagestats ==1.4.1
+    - specview ==0.1      
 
-    - stsci.ndimage ==0.10.1
+    - stginga ==0.0.0     
 
-    - stsci.numdisplay ==1.6.1
+- **stsci-data-analysis-1.0.0 (np110py35_0)**
 
-    - stsci.skypac ==0.9  
+    - asdf ==1.0.2        
 
-    - stsci.sphere ==0.2  
+    - astroimtools ==0.1  
 
-    - stsci.sphinxext ==1.2.2
+    - astropy >=1.1       
 
-    - stsci.stimage ==0.2.1
+    - asv ==0.1.1         
 
-    - stsci.tools ==3.4.1 
+    - cube-tools ==0.0.0  
 
-    - stwcs ==1.2.3       
+    - numpy 1.10*         
 
-    - wfc3tools ==1.3.1   
+    - python 3.5*         
 
-    - wfpc2tools ==1.0.3  
+    - specview ==0.1      
 
-- **stsci-hst-1.0.0 (np110py34_0)**
+    - stginga ==0.0.0     
 
-    - acstools ==2.0.0    
+- **stsci-hst-1.0.4 (np111py27_0)**
 
-    - astrolib.coords ==0.39.6
+    - acstools >=2.0.0    
 
     - astropy >=1.1       
 
-    - calcos ==3.1.3      
+    - calcos >=3.1.8      
 
-    - costools ==1.2.1    
+    - costools >=1.2.1    
 
-    - crds ==0.0.0        
+    - crds >=7.0.1        
 
-    - d2to1 ==0.2.12      
+    - d2to1 >=0.2.12      
 
-    - drizzlepac ==2.1.3  
+    - drizzlepac >=2.1.3  
 
-    - fitsblender ==0.2.6 
+    - fitsblender >=0.2.6 
 
-    - hstcal ==1.0.0      
+    - hstcal >=1.0.0      
 
-    - nictools ==1.1.3    
+    - nictools >=1.1.3    
 
-    - numpy 1.10*         
+    - numpy 1.11*         
 
-    - purge_path >=0.0.1  
+    - purge_path >=1.0.0  
 
-    - pyregion ==1.1.2    
+    - pyregion >=1.1.2    
 
-    - pysynphot ==0.9.8.2 
+    - pysynphot >=0.9.8.2 
 
-    - python 3.4*         
-
-    - pywcs ==1.12.1      
-
-    - reftools ==1.7.1    
+    - python 2.7*         
 
-    - stistools ==1.1     
+    - reftools >=1.7.1    
 
-    - stsci.convolve ==2.1.3
+    - stistools >=1.1     
 
-    - stsci.distutils ==0.3.8
+    - stsci.convolve >=2.1.3
 
-    - stsci.image ==2.2.0 
+    - stsci.distutils >=0.3.8
 
-    - stsci.imagemanip ==1.1.2
+    - stsci.image >=2.2.0 
 
-    - stsci.imagestats ==1.4.1
+    - stsci.imagemanip >=1.1.2
 
-    - stsci.ndimage ==0.10.1
+    - stsci.imagestats >=1.4.1
 
-    - stsci.numdisplay ==1.6.1
+    - stsci.ndimage >=0.10.1
 
-    - stsci.skypac ==0.9  
+    - stsci.numdisplay >=1.6.1
 
-    - stsci.sphere ==0.2  
+    - stsci.skypac >=0.9  
 
-    - stsci.sphinxext ==1.2.2
+    - stsci.sphere >=0.2  
 
-    - stsci.stimage ==0.2.1
+    - stsci.sphinxext >=1.2.2
 
-    - stsci.tools ==3.4.1 
+    - stsci.stimage >=0.2.1
 
-    - stwcs ==1.2.3       
+    - stsci.tools >=3.4.1 
 
-    - wfc3tools ==1.3.1   
+    - stwcs >=1.2.3       
 
-    - wfpc2tools ==1.0.3  
+    - wfc3tools >=1.3.1   
 
-- **stsci-hst-1.0.0 (np110py27_0)**
+    - wfpc2tools >=1.0.3  
 
-    - acstools ==2.0.0    
+- **stsci-hst-1.0.4 (np111py35_0)**
 
-    - astrolib.coords ==0.39.6
+    - acstools >=2.0.0    
 
     - astropy >=1.1       
 
-    - calcos ==3.1.3      
-
-    - costools ==1.2.1    
+    - calcos >=3.1.8      
 
-    - crds ==0.0.0        
+    - costools >=1.2.1    
 
-    - d2to1 ==0.2.12      
+    - crds >=7.0.1        
 
-    - drizzlepac ==2.1.3  
+    - d2to1 >=0.2.12      
 
-    - fitsblender ==0.2.6 
+    - drizzlepac >=2.1.3  
 
-    - hstcal ==1.0.0      
+    - fitsblender >=0.2.6 
 
-    - nictools ==1.1.3    
+    - hstcal >=1.0.0      
 
-    - numpy 1.10*         
+    - nictools >=1.1.3    
 
-    - purge_path >=0.0.1  
+    - numpy 1.11*         
 
-    - pyregion ==1.1.2    
+    - purge_path >=1.0.0  
 
-    - pysynphot ==0.9.8.2 
+    - pyregion >=1.1.2    
 
-    - python 2.7*         
+    - pysynphot >=0.9.8.2 
 
-    - pywcs ==1.12.1      
+    - python 3.5*         
 
-    - reftools ==1.7.1    
+    - reftools >=1.7.1    
 
-    - stistools ==1.1     
+    - stistools >=1.1     
 
-    - stsci.convolve ==2.1.3
+    - stsci.convolve >=2.1.3
 
-    - stsci.distutils ==0.3.8
+    - stsci.distutils >=0.3.8
 
-    - stsci.image ==2.2.0 
+    - stsci.image >=2.2.0 
 
-    - stsci.imagemanip ==1.1.2
+    - stsci.imagemanip >=1.1.2
 
-    - stsci.imagestats ==1.4.1
+    - stsci.imagestats >=1.4.1
 
-    - stsci.ndimage ==0.10.1
+    - stsci.ndimage >=0.10.1
 
-    - stsci.numdisplay ==1.6.1
+    - stsci.numdisplay >=1.6.1
 
-    - stsci.skypac ==0.9  
+    - stsci.skypac >=0.9  
 
-    - stsci.sphere ==0.2  
+    - stsci.sphere >=0.2  
 
-    - stsci.sphinxext ==1.2.2
+    - stsci.sphinxext >=1.2.2
 
-    - stsci.stimage ==0.2.1
+    - stsci.stimage >=0.2.1
 
-    - stsci.tools ==3.4.1 
+    - stsci.tools >=3.4.1 
 
-    - stwcs ==1.2.3       
+    - stwcs >=1.2.3       
 
-    - wfc3tools ==1.3.1   
+    - wfc3tools >=1.3.1   
 
-    - wfpc2tools ==1.0.3  
+    - wfpc2tools >=1.0.3  
 
 linux-64 packages
 ------------------------
@@ -415,10 +359,18 @@ linux-64 packages
 
 - acstools-2.0.0
 
+- acstools-2.0.2
+
+- acstools-2.0.4
+
 - appdirs-1.4.0
 
+- aprio-1.0.1
+
 - asdf-1.0.2
 
+- asdf-1.0.3
+
 - asdf-standard-1.0.0
 
 - astroimtools-0.1
@@ -429,18 +381,40 @@ linux-64 packages
 
 - calcos-3.1.3
 
+- calcos-3.1.7
+
+- calcos-3.1.8
+
 - cfitsio-3.370
 
 - costools-1.2.1
 
 - crds-0.0.0
 
+- crds-6.0.0
+
+- crds-7.0.1
+
 - cube-tools-0.0.0
 
+- cube-tools-0.0.1
+
 - d2to1-0.2.12
 
+- decorator-4.0.9
+
+- drizzle-1.1
+
 - drizzlepac-2.1.3
 
+- drizzlepac-2.1.4
+
+- drizzlepac-2.1.5
+
+- drizzlepac-2.1.6
+
+- ds9-7.1
+
 - ds9-7.4
 
 - fftw-3.3.4
@@ -449,12 +423,26 @@ linux-64 packages
 
 - ginga-2.5.20151215011852
 
+- ginga-2.5.20160627100500
+
+- ginga-2.5.20160706100500
+
+- ginga-2.5.20160801083400
+
+- glue-vispy-viewers-0.4
+
+- glueviz-0.8.2
+
 - gwcs-0.5
 
 - gwcs-0.5.1
 
+- gwcs-0.6rc1
+
 - hstcal-1.0.0
 
+- hstcal-1.0.1
+
 - htc_utils-0.1
 
 - imexam-0.5.2
@@ -469,22 +457,44 @@ linux-64 packages
 
 - nictools-1.1.3
 
+- opuscoords-1.0.2
+
+- pandokia-1.3.11
+
 - photutils-0.2.1
 
+- photutils-0.2.2
+
 - poppy-0.4.0
 
+- poppy-0.5.0
+
 - purge_path-1.0.0
 
+- pydrizzle-6.4.4
+
 - pyds9-1.8.1
 
 - pyfftw-0.9.2
 
+- pyqtgraph-0.9.10
+
+- pyqtgraph-0.9.11
+
 - pyraf-2.1.10
 
+- pyraf-2.1.11
+
 - pyregion-1.1.2
 
 - pysynphot-0.9.8.2
 
+- pysynphot-0.9.8.3
+
+- pysynphot-0.9.8.4
+
+- python-daemon-2.0.5
+
 - pytools-2016.1
 
 - pywcs-1.12.1
@@ -493,22 +503,62 @@ linux-64 packages
 
 - reftools-1.7.1
 
+- reftools-1.7.3
+
 - relic-1.0.4
 
+- relic-1.0.5
+
+- selenium-2.49.2
+
 - shunit2-2.0.3
 
+- specutils-0.2.1
+
 - specview-0.1
 
+- specviz-0.1.2rc3
+
+- specviz-0.2.0rc3
+
+- specviz-0.2.1rc4
+
+- specviz-0.2.1rc5
+
+- sphere-1.0.6
+
+- sphere-1.0.7
+
+- sphinx_rtd_theme-0.1.9
+
+- sphinxcontrib-programoutput-0.8
+
 - stginga-0.0.0
 
+- stginga-0.1
+
+- stginga-0.1.1
+
+- stginga-0.1.2
+
 - stistools-1.1
 
 - stsci-1.0.0
 
+- stsci-1.0.1
+
 - stsci-data-analysis-1.0.0
 
 - stsci-hst-1.0.0
 
+- stsci-hst-1.0.1
+
+- stsci-hst-1.0.2
+
+- stsci-hst-1.0.3
+
+- stsci-hst-1.0.4
+
 - stsci.convolve-2.1.3
 
 - stsci.distutils-0.3.8
@@ -539,8 +589,12 @@ linux-64 packages
 
 - webbpsf-0.4.0
 
+- webbpsf-0.5.0
+
 - webbpsf-data-0.4.0
 
+- webbpsf-data-0.5.0
+
 - wfc3tools-1.3.1
 
 - wfpc2tools-1.0.3
@@ -551,71 +605,33 @@ osx-64 metapackages
 ------------------------
 
 
-- **stsci-1.0.0 (np110py34_0)**
-
-    - astropy >=1.1       
-
-    - cfitsio ==3.370     
-
-    - d2to1 ==0.2.12      
-
-    - ds9 ==7.4           
-
-    - fftw ==3.3.4        
-
-    - htc_utils >=0.1     
-
-    - imexam ==0.5.2      
-
-    - numpy 1.10*         
-
-    - photutils ==0.2.1   
-
-    - poppy ==0.4.0       
-
-    - purge_path >=0.0.1  
-
-    - pyds9 ==1.8.1       
-
-    - pyfftw ==0.9.2      
-
-    - python 3.4*         
-
-    - stsci-data-analysis 
-
-    - stsci-hst           
-
-    - webbpsf ==0.4.0     
-
-    - webbpsf-data ==0.4.0
-
-- **stsci-1.0.0 (np110py27_0)**
+- **stsci-1.0.1 (np111py27_0)**
 
     - astropy >=1.1       
 
-    - cfitsio ==3.370     
+    - cfitsio >=3.370     
 
-    - d2to1 ==0.2.12      
+    - d2to1 >=0.2.12      
 
-    - ds9 ==7.4           
+    - ds9 >=7.1           
 
-    - fftw ==3.3.4        
+    - fftw >=3.3.4        
 
     - htc_utils >=0.1     
 
-    - imexam ==0.5.2      
+    - imexam >=0.5.2      
 
-    - numpy 1.10*         
+    - numpy 1.11*         
 
-    - photutils ==0.2.1   
+    - photutils >=0.2.1   
 
-    - poppy ==0.4.0       
+    - poppy >=0.4.0       
 
-    - purge_path >=0.0.1  
+    - purge_path >=1.0.0  
 
-    - pyds9 ==1.8.1       
+    - pyds9 >=1.8.1       
 
-    - pyfftw ==0.9.2      
+    - pyfftw >=0.9.2      
 
     - python 2.7*         
 
@@ -623,37 +639,37 @@ osx-64 metapackages
 
     - stsci-hst           
 
-    - webbpsf ==0.4.0     
+    - webbpsf >=0.4.0     
 
-    - webbpsf-data ==0.4.0
+    - webbpsf-data >=0.4.0
 
-- **stsci-1.0.0 (np110py35_0)**
+- **stsci-1.0.1 (np111py35_0)**
 
     - astropy >=1.1       
 
-    - cfitsio ==3.370     
+    - cfitsio >=3.370     
 
-    - d2to1 ==0.2.12      
+    - d2to1 >=0.2.12      
 
-    - ds9 ==7.4           
+    - ds9 >=7.1           
 
-    - fftw ==3.3.4        
+    - fftw >=3.3.4        
 
     - htc_utils >=0.1     
 
-    - imexam ==0.5.2      
+    - imexam >=0.5.2      
 
-    - numpy 1.10*         
+    - numpy 1.11*         
 
-    - photutils ==0.2.1   
+    - photutils >=0.2.1   
 
-    - poppy ==0.4.0       
+    - poppy >=0.4.0       
 
-    - purge_path >=0.0.1  
+    - purge_path >=1.0.0  
 
-    - pyds9 ==1.8.1       
+    - pyds9 >=1.8.1       
 
-    - pyfftw ==0.9.2      
+    - pyfftw >=0.9.2      
 
     - python 3.5*         
 
@@ -661,29 +677,29 @@ osx-64 metapackages
 
     - stsci-hst           
 
-    - webbpsf ==0.4.0     
+    - webbpsf >=0.4.0     
 
-    - webbpsf-data ==0.4.0
+    - webbpsf-data >=0.4.0
 
-- **stsci-data-analysis-1.0.0 (np110py27_0)**
+- **stsci-data-analysis-1.0.0 (np111py27_2)**
 
-    - asdf ==1.0.2        
+    - asdf >=1.0.2        
 
-    - astroimtools ==0.1  
+    - astroimtools >=0.1  
 
     - astropy >=1.1       
 
-    - asv ==0.1.1         
+    - asv >=0.1.1         
 
-    - cube-tools ==0.0.0  
+    - cube-tools >=0.0.0  
 
-    - numpy 1.10*         
+    - numpy 1.11*         
 
     - python 2.7*         
 
-    - specview ==0.1      
+    - specview >=0.1      
 
-    - stginga ==0.0.0     
+    - stginga >=0.1       
 
 - **stsci-data-analysis-1.0.0 (np110py35_0)**
 
@@ -725,215 +741,177 @@ osx-64 metapackages
 
     - stginga ==0.0.0     
 
-- **stsci-hst-1.0.0 (np110py35_0)**
+- **stsci-data-analysis-1.0.0 (np111py35_2)**
 
-    - acstools ==2.0.0    
+    - asdf >=1.0.2        
 
-    - astrolib.coords ==0.39.6
+    - astroimtools >=0.1  
 
     - astropy >=1.1       
 
-    - calcos ==3.1.3      
-
-    - costools ==1.2.1    
-
-    - crds ==0.0.0        
-
-    - d2to1 ==0.2.12      
+    - asv >=0.1.1         
 
-    - drizzlepac ==2.1.3  
+    - cube-tools >=0.0.0  
 
-    - fitsblender ==0.2.6 
-
-    - hstcal ==1.0.0      
-
-    - nictools ==1.1.3    
-
-    - numpy 1.10*         
-
-    - purge_path >=0.0.1  
-
-    - pyregion ==1.1.2    
-
-    - pysynphot ==0.9.8.2 
+    - numpy 1.11*         
 
     - python 3.5*         
 
-    - pywcs ==1.12.1      
-
-    - reftools ==1.7.1    
+    - specview >=0.1      
 
-    - stistools ==1.1     
+    - stginga >=0.1       
 
-    - stsci.convolve ==2.1.3
-
-    - stsci.distutils ==0.3.8
-
-    - stsci.image ==2.2.0 
-
-    - stsci.imagemanip ==1.1.2
-
-    - stsci.imagestats ==1.4.1
-
-    - stsci.ndimage ==0.10.1
-
-    - stsci.numdisplay ==1.6.1
+- **stsci-data-analysis-1.0.0 (np110py27_0)**
 
-    - stsci.skypac ==0.9  
+    - asdf ==1.0.2        
 
-    - stsci.sphere ==0.2  
+    - astroimtools ==0.1  
 
-    - stsci.sphinxext ==1.2.2
+    - astropy >=1.1       
 
-    - stsci.stimage ==0.2.1
+    - asv ==0.1.1         
 
-    - stsci.tools ==3.4.1 
+    - cube-tools ==0.0.0  
 
-    - stwcs ==1.2.3       
+    - numpy 1.10*         
 
-    - wfc3tools ==1.3.1   
+    - python 2.7*         
 
-    - wfpc2tools ==1.0.3  
+    - specview ==0.1      
 
-- **stsci-hst-1.0.0 (np110py34_0)**
+    - stginga ==0.0.0     
 
-    - acstools ==2.0.0    
+- **stsci-hst-1.0.4 (np111py35_0)**
 
-    - astrolib.coords ==0.39.6
+    - acstools >=2.0.0    
 
     - astropy >=1.1       
 
-    - calcos ==3.1.3      
+    - calcos >=3.1.8      
 
-    - costools ==1.2.1    
+    - costools >=1.2.1    
 
-    - crds ==0.0.0        
+    - crds >=7.0.1        
 
-    - d2to1 ==0.2.12      
+    - d2to1 >=0.2.12      
 
-    - drizzlepac ==2.1.3  
+    - drizzlepac >=2.1.3  
 
-    - fitsblender ==0.2.6 
+    - fitsblender >=0.2.6 
 
-    - hstcal ==1.0.0      
+    - hstcal >=1.0.0      
 
-    - nictools ==1.1.3    
+    - nictools >=1.1.3    
 
-    - numpy 1.10*         
-
-    - purge_path >=0.0.1  
+    - numpy 1.11*         
 
-    - pyregion ==1.1.2    
+    - purge_path >=1.0.0  
 
-    - pysynphot ==0.9.8.2 
+    - pyregion >=1.1.2    
 
-    - python 3.4*         
+    - pysynphot >=0.9.8.2 
 
-    - pywcs ==1.12.1      
-
-    - reftools ==1.7.1    
+    - python 3.5*         
 
-    - stistools ==1.1     
+    - reftools >=1.7.1    
 
-    - stsci.convolve ==2.1.3
+    - stistools >=1.1     
 
-    - stsci.distutils ==0.3.8
+    - stsci.convolve >=2.1.3
 
-    - stsci.image ==2.2.0 
+    - stsci.distutils >=0.3.8
 
-    - stsci.imagemanip ==1.1.2
+    - stsci.image >=2.2.0 
 
-    - stsci.imagestats ==1.4.1
+    - stsci.imagemanip >=1.1.2
 
-    - stsci.ndimage ==0.10.1
+    - stsci.imagestats >=1.4.1
 
-    - stsci.numdisplay ==1.6.1
+    - stsci.ndimage >=0.10.1
 
-    - stsci.skypac ==0.9  
+    - stsci.numdisplay >=1.6.1
 
-    - stsci.sphere ==0.2  
+    - stsci.skypac >=0.9  
 
-    - stsci.sphinxext ==1.2.2
+    - stsci.sphere >=0.2  
 
-    - stsci.stimage ==0.2.1
+    - stsci.sphinxext >=1.2.2
 
-    - stsci.tools ==3.4.1 
+    - stsci.stimage >=0.2.1
 
-    - stwcs ==1.2.3       
+    - stsci.tools >=3.4.1 
 
-    - wfc3tools ==1.3.1   
+    - stwcs >=1.2.3       
 
-    - wfpc2tools ==1.0.3  
+    - wfc3tools >=1.3.1   
 
-- **stsci-hst-1.0.0 (np110py27_0)**
+    - wfpc2tools >=1.0.3  
 
-    - acstools ==2.0.0    
+- **stsci-hst-1.0.4 (np111py27_0)**
 
-    - astrolib.coords ==0.39.6
+    - acstools >=2.0.0    
 
     - astropy >=1.1       
 
-    - calcos ==3.1.3      
+    - calcos >=3.1.8      
 
-    - costools ==1.2.1    
+    - costools >=1.2.1    
 
-    - crds ==0.0.0        
+    - crds >=7.0.1        
 
-    - d2to1 ==0.2.12      
+    - d2to1 >=0.2.12      
 
-    - drizzlepac ==2.1.3  
+    - drizzlepac >=2.1.3  
 
-    - fitsblender ==0.2.6 
+    - fitsblender >=0.2.6 
 
-    - hstcal ==1.0.0      
+    - hstcal >=1.0.0      
 
-    - nictools ==1.1.3    
+    - nictools >=1.1.3    
 
-    - numpy 1.10*         
+    - numpy 1.11*         
 
-    - purge_path >=0.0.1  
+    - purge_path >=1.0.0  
 
-    - pyregion ==1.1.2    
+    - pyregion >=1.1.2    
 
-    - pysynphot ==0.9.8.2 
+    - pysynphot >=0.9.8.2 
 
     - python 2.7*         
 
-    - pywcs ==1.12.1      
-
-    - reftools ==1.7.1    
+    - reftools >=1.7.1    
 
-    - stistools ==1.1     
+    - stistools >=1.1     
 
-    - stsci.convolve ==2.1.3
+    - stsci.convolve >=2.1.3
 
-    - stsci.distutils ==0.3.8
+    - stsci.distutils >=0.3.8
 
-    - stsci.image ==2.2.0 
+    - stsci.image >=2.2.0 
 
-    - stsci.imagemanip ==1.1.2
+    - stsci.imagemanip >=1.1.2
 
-    - stsci.imagestats ==1.4.1
+    - stsci.imagestats >=1.4.1
 
-    - stsci.ndimage ==0.10.1
+    - stsci.ndimage >=0.10.1
 
-    - stsci.numdisplay ==1.6.1
+    - stsci.numdisplay >=1.6.1
 
-    - stsci.skypac ==0.9  
+    - stsci.skypac >=0.9  
 
-    - stsci.sphere ==0.2  
+    - stsci.sphere >=0.2  
 
-    - stsci.sphinxext ==1.2.2
+    - stsci.sphinxext >=1.2.2
 
-    - stsci.stimage ==0.2.1
+    - stsci.stimage >=0.2.1
 
-    - stsci.tools ==3.4.1 
+    - stsci.tools >=3.4.1 
 
-    - stwcs ==1.2.3       
+    - stwcs >=1.2.3       
 
-    - wfc3tools ==1.3.1   
+    - wfc3tools >=1.3.1   
 
-    - wfpc2tools ==1.0.3  
+    - wfpc2tools >=1.0.3  
 
 osx-64 packages
 ------------------------
@@ -941,10 +919,18 @@ osx-64 packages
 
 - acstools-2.0.0
 
+- acstools-2.0.2
+
+- acstools-2.0.4
+
 - appdirs-1.4.0
 
+- aprio-1.0.1
+
 - asdf-1.0.2
 
+- asdf-1.0.3
+
 - asdf-standard-1.0.0
 
 - astroimtools-0.1
@@ -955,18 +941,40 @@ osx-64 packages
 
 - calcos-3.1.3
 
+- calcos-3.1.7
+
+- calcos-3.1.8
+
 - cfitsio-3.370
 
 - costools-1.2.1
 
 - crds-0.0.0
 
+- crds-6.0.0
+
+- crds-7.0.1
+
 - cube-tools-0.0.0
 
+- cube-tools-0.0.1
+
 - d2to1-0.2.12
 
+- decorator-4.0.9
+
+- drizzle-1.1
+
 - drizzlepac-2.1.3
 
+- drizzlepac-2.1.4
+
+- drizzlepac-2.1.5
+
+- drizzlepac-2.1.6
+
+- ds9-7.1
+
 - ds9-7.4
 
 - fftw-3.3.4
@@ -975,12 +983,26 @@ osx-64 packages
 
 - ginga-2.5.20151215011852
 
+- ginga-2.5.20160627100500
+
+- ginga-2.5.20160706100500
+
+- ginga-2.5.20160801083400
+
+- glue-vispy-viewers-0.4
+
+- glueviz-0.8.2
+
 - gwcs-0.5
 
 - gwcs-0.5.1
 
+- gwcs-0.6rc1
+
 - hstcal-1.0.0
 
+- hstcal-1.0.1
+
 - htc_utils-0.1
 
 - imexam-0.5.2
@@ -995,28 +1017,56 @@ osx-64 packages
 
 - nictools-1.1.3
 
+- opuscoords-1.0.2
+
+- pandokia-1.3.11
+
 - photutils-0.2.1
 
+- photutils-0.2.2
+
 - poppy-0.4.0
 
+- poppy-0.5.0
+
 - purge_path-1.0.0
 
+- pydrizzle-6.4.4
+
 - pyds9-1.8.1
 
 - pyfftw-0.9.2
 
+- pyobjc-core-3.0.4
+
 - pyobjc-core-3.1.1
 
+- pyobjc-framework-cocoa-3.0.4
+
 - pyobjc-framework-cocoa-3.1.1
 
+- pyobjc-framework-quartz-3.0.4
+
 - pyobjc-framework-quartz-3.1.1
 
+- pyqtgraph-0.9.10
+
+- pyqtgraph-0.9.11
+
 - pyraf-2.1.10
 
+- pyraf-2.1.11
+
 - pyregion-1.1.2
 
 - pysynphot-0.9.8.2
 
+- pysynphot-0.9.8.3
+
+- pysynphot-0.9.8.4
+
+- python-daemon-2.0.5
+
 - pytools-2016.1
 
 - pywcs-1.12.1
@@ -1025,22 +1075,64 @@ osx-64 packages
 
 - reftools-1.7.1
 
+- reftools-1.7.3
+
 - relic-1.0.4
 
+- relic-1.0.5
+
+- selenium-2.49.2
+
+- sextractor-2.19.5
+
 - shunit2-2.0.3
 
+- specutils-0.2.1
+
 - specview-0.1
 
+- specviz-0.1.2rc3
+
+- specviz-0.2.0rc3
+
+- specviz-0.2.1rc5
+
+- sphere-1.0.6
+
+- sphere-1.0.7
+
+- sphinx_rtd_theme-0.1.9
+
+- sphinxcontrib-programoutput-0.8
+
 - stginga-0.0.0
 
+- stginga-0.1
+
+- stginga-0.1.1
+
+- stginga-0.1.2
+
 - stistools-1.1
 
 - stsci-1.0.0
 
+- stsci-1.0.1
+
+- stsci-data-analysis-0.0.0.dev0
+
 - stsci-data-analysis-1.0.0
 
 - stsci-hst-1.0.0
 
+- stsci-hst-1.0.1
+
+- stsci-hst-1.0.2
+
+- stsci-hst-1.0.3
+
+- stsci-hst-1.0.4
+
 - stsci.convolve-2.1.3
 
 - stsci.distutils-0.3.8
@@ -1071,8 +1163,12 @@ osx-64 packages
 
 - webbpsf-0.4.0
 
+- webbpsf-0.5.0
+
 - webbpsf-data-0.4.0
 
+- webbpsf-data-0.5.0
+
 - wfc3tools-1.3.1
 
 - wfpc2tools-1.0.3
diff --git a/source/release_notes.rst b/source/release_notes.rst
index 15f66ed..640aea7 100644
--- a/source/release_notes.rst
+++ b/source/release_notes.rst
@@ -4,6 +4,35 @@ Release Notes
 ACSTOOLS
 --------
 
+ACSTOOLS v2.0.4 Release Notes
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+*2016-07-28 18:50:50+00:00*
+
+``stsci.xxx``, ``scipy``, and ``scikit-image`` are now *optional*
+packages. That is, ``acstools`` would install without them but affected
+task(s) will complain if they are missing.
+
+ACSTOOLS v2.0.3 Release Notes
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+*2016-07-28 17:27:15+00:00*
+
+Re-organize package for a cleaner look. Executable scripts are now entry
+points (for Windows compatibility). Version tagging is now controlled by
+``relic`` submodule. Miscellaneous clean ups that should not affect
+functionality.
+
+ACSTOOLS v2.0.2 Release Notes
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+*2016-06-03 20:42:49+00:00*
+
+Bug fix release with a fix for outdated skimage import in satellite
+detection tool.
+
+References: #6
+
 ACSTOOLS v2.0.1 Release Notes
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
@@ -214,6 +243,22 @@ Added code to pass brftab reference file to timetag.getWavecalOffsets so
 that the Active Area can be determined at the time the offsets are
 calculated.
 
+CRDS
+----
+
+Server-side code for opus-2016.1-4
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+*None*
+
+This release includes context pickling optimizations to address Isilon
+file system performance issues.
+
+CUBE-TOOLS
+----------
+
+*2016-08-03 15:22:50+00:00*
+
 DRIZZLEPAC
 ----------
 
@@ -329,6 +374,16 @@ Feb 2016. It primarily includes bug fixes; namely,
 HSTCAL
 ------
 
+HSTCAL v1.0.1 Release Notes
+~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+*2016-07-07 19:36:46+00:00*
+
+This release is to accommodate CALACS processing for new ACS subarrays
+added by FSW change done in May 2016. Particularly, BLEVCORR is modified
+to trim virtual overscans off the new subarrays (old subarrays do not
+have virtual overscans). No changes are made for CALWF3 and CALSTIS.
+
 HSTCAL v1.0.0 Release Notes
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
@@ -426,9 +481,49 @@ ACS
 
 -  Fixed memory leaks (non-critical).
 
+JWST\_VISIBILITY
+----------------
+
+*2016-08-01 19:12:06+00:00*
+
+The first tagged release of the tool for internal and external testing.
+Target visibility plots from this tool should **always** be checked
+against APT for consistency, as this tool does not account for all of
+the same constraints (and is not intended to).
+
+PYRAF
+-----
+
+Version 2.1.10.1
+~~~~~~~~~~~~~~~~
+
+*2016-06-23 15:32:40+00:00*
+
+This is not a real release of PyRAF per-se, but it's first git/github
+tag.
+
 PYSYNPHOT
 ---------
 
+PySynphot v0.9.8.4 Release Notes
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+*2016-08-15 15:50:59+00:00*
+
+Fixed a bug of inconsistent ``waveset`` definitions across different
+objects. Cleaned up setup files. Now uses ``relic`` submodule for
+version tagging.
+
+PySynphot v0.9.8.3 Release Notes
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+*2016-07-07 21:09:08+00:00*
+
+Moved ``data``, ``test``, and ``src`` directories one-level down for
+AstroConda. Minor documentation related updates. Typical users should
+not see significant changes between this release and the previous
+release of 0.9.8.2.
+
 PySynphot v0.9.8.2 Release Notes
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
@@ -451,6 +546,23 @@ October 19, 2015:
 REFTOOLS
 --------
 
+REFTOOLS v1.7.3 Release Notes
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+*2016-08-08 18:17:10+00:00*
+
+Fix AstroConda build by making TEAL import in ``tdspysyn`` completely
+optional.
+
+REFTOOLS v1.7.2 Release Notes
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+*2016-08-02 15:30:44+00:00*
+
+Reorganized and cleaned up package. Updated documentation. Marked some
+tests as expected failures. Overall, none of these changes should affect
+end-user.
+
 REFTOOLS v1.7.1 Release Notes
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
@@ -478,6 +590,48 @@ Pre-release for May2015 JWST DA User Training
 SPECVIZ
 -------
 
+v0.2.1rc5
+~~~~~~~~~
+
+*2016-07-19 13:20:03+00:00*
+
+Same as RC4, except we fixed ``ConfigParser`` compability with Python 3.
+
+v0.2.1rc4
+~~~~~~~~~
+
+*2016-07-12 18:05:38+00:00*
+
+This release incorporates the specutils package, replacing the
+previously used base spectrum object with the specutils object.
+
+v0.2.0rc3
+~~~~~~~~~
+
+*2016-06-20 23:44:13+00:00*
+
+This release contains fixes and usability improvements from our first
+round of internal testing. Its main priorities include:
+
+1. Remove dependency on Qt Creator
+
+2. Reincorporate all our tools as plugins
+
+It introduces a new plugin architecture for user-created extensions.
+
+v0.1.2rc3
+~~~~~~~~~
+
+*2016-05-18 16:19:40+00:00*
+
+Minor improvements to:
+
+-  unit behaviors
+
+-  modelling behaviors
+
+-  updated installation documentation
+
 v0.1.1rc3
 ~~~~~~~~~
 
@@ -485,16 +639,16 @@ v0.1.1rc3
 
 Minor bug fixes.
 
-v0.1rc3
-~~~~~~~
+v0.1.0rc3
+~~~~~~~~~
 
 *2016-03-17 19:14:04+00:00*
 
 Feature complete (for this release) version of SpecViz. However,
 usability bugs and minor tweaks are still to be expected.
 
-v0.1rc2
-~~~~~~~
+v0.1.0rc2
+~~~~~~~~~
 
 *2016-02-15 17:55:20+00:00*
 
@@ -506,6 +660,32 @@ v0.1rc2
 
 -  Bug fixes
 
+STGINGA
+-------
+
+stginga 0.1.2 Release Notes
+~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+*2016-07-12 20:30:51+00:00*
+
+Added background mean calculation to ``SNRCalc`` local plugin. Removed
+``unicode_literals`` from imports.
+
+stginga 0.1.1 Release Notes
+~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+*2016-07-07 18:40:22+00:00*
+
+This is a bug fix release that fixed ConfigParser error in Python 3.
+Also updated astropy\_helpers to v1.2.
+
+First stginga release
+~~~~~~~~~~~~~~~~~~~~~
+
+*2016-06-21 21:23:26+00:00*
+
+Mostly working. Why not?
+
 STSCI.TOOLS
 -----------
 
diff --git a/source/updating.rst b/source/updating.rst
index f897e2c..24e0018 100644
--- a/source/updating.rst
+++ b/source/updating.rst
@@ -2,9 +2,7 @@
 Keeping AstroConda "Like New"
 *****************************
 
-Anaconda's package manager, Conda, will not automatically update unless a newer version of a package is detected during
-a routine package installation. Suffice to say, unless you keep your packages up to date with ``conda update``, the
-packages installed in your Anaconda distribution will remain relatively static.
+Anaconda's package manager, Conda, will not automatically update unless a newer version of a package is detected during a routine package installation. Suffice to say, unless you keep your packages up to date with ``conda update``, the packages installed in your Anaconda distribution will remain relatively static.
 
 Updating AstroConda
 ===================
@@ -18,10 +16,7 @@ Updating the Release
 
     $ conda update -n astroconda stsci
 
-This is best used by individuals that favor software stability over receiving the "bleeding edge". Remember, updating the
-``stsci`` metapackage only effects packages part of the **official public release** of our software. Packages that are
-provided by the AstroConda repository, but are not controlled by the ``stsci`` metapackage **will not receive updates**.
-This holds true for all other metapackages as well (e.g. stsci-hst, stsci-jwst, stsci-data-analysis, etc).
+This is best used by individuals that favor software stability over receiving the "bleeding edge". Remember, updating the ``stsci`` metapackage only effects packages part of the **official public release** of our software. Packages that are provided by the AstroConda repository, but are not controlled by the ``stsci`` metapackage **will not receive updates**. This holds true for all other metapackages as well (e.g. stsci-hst, stsci-jwst, stsci-data-analysis, etc).
 
 Updating All Packages
 ---------------------
@@ -32,8 +27,7 @@ Updating All Packages
 
 This will update the ``stsci`` metapackage, as well all other packages installed in your enviroment. [1]_
 
-This updates **all packages** regardless if they were installed from AstroConda, Continuum, Inc.,
-or other third party repositories defined in ``$HOME/.condarc``.
+This updates **all packages** regardless if they were installed from AstroConda, Continuum, Inc., or other third party repositories defined in ``$HOME/.condarc``.
 
 (`ref <http://conda.pydata.org/docs/using/pkgs.html#package-update>`__)
 
@@ -45,15 +39,13 @@ Updating Packages Individually
 
     $ conda update -n astroconda stsci.tools
 
-If you are interested in receiving updates for a particular package, then this method is for you. Be aware that packages
-may depend on other packages, so the total list of package updates returned by this command will vary.
+If you are interested in receiving updates for a particular package, then this method is for you. Be aware that packages may depend on other packages, so the total list of package updates returned by this command will vary.
 
 
 Downgrading Packages
 ====================
 
-Did a recent update break your code? Don't wait around for a bugfix... Keep working. For example, if a bug is introduced
-into ``stsci.tools``, you can easily downgrade it to a known-good version:
+Did a recent update break your code? Don't wait around for a bugfix... Keep working. For example, if a bug is introduced into ``stsci.tools``, you can easily downgrade it to a known-good version:
 
 .. code-block:: sh
 
@@ -79,18 +71,14 @@ Pinning Packages
 
 .. caution:: Pinning packages has the potential to break Conda. Only pin packages as a last resort.
 
-Let's take the previous example one step further... Imagine ``stsci.tools`` is broken, and the hotfix release of ``3.4.2``
-only partially solved the original issue. Now what? You still need to receive updates to other packages, but
-``stsci.tools`` keeps trying to update back to ``3.4.2`` every time you touch ``conda update``.
+Let's take the previous example one step further... Imagine ``stsci.tools`` is broken, and the hotfix release of ``3.4.2`` only partially solved the original issue. Now what? You still need to receive updates to other packages, but ``stsci.tools`` keeps trying to update back to ``3.4.2`` every time you touch ``conda update``.
 
 
 .. code-block:: sh
 
     $ echo "stsci.tools <=3.4.0" > ${CONDA_ENV_PATH}/conda-meta/pinned
 
-From now on, future calls to ``conda update`` will omit ``stsci.tools`` while performing dependency resolution. However,
-a clear side-effect of this will also be losing the ability to update packages that depend strictly on version ``3.4.2``.
-Although this is not a permanent solution it can prove useful in a bad situation.
+From now on, future calls to ``conda update`` will omit ``stsci.tools`` while performing dependency resolution. However, a clear side-effect of this will also be losing the ability to update packages that depend strictly on version ``3.4.2``. Although this is not a permanent solution it can prove useful in a bad situation.
 
 (`ref <http://conda.pydata.org/docs/faq.html?highlight=pinning#pinning-packages>`__)