Revise instructions on where to get build products

documentation/ADMINISTRATA.rst

@@ -214,21 +214,19 @@ the tagged build products and place in :file:`dist/`:
   :file:`FiPy-x.y.tar.gz`
     From CircleCI_ `build-binaries` Artifacts
 
-  :file:`FiPy-x.y.win32.zip`
-    From AppVeyor_ Artifacts
-
-Clean the working copy::
-
-    $ git clean -fd
+  :file:`~/project/documentation/_build/latex/fipy.pdf`
+    From CircleCI_ `build-36-docs` Artifacts
 
-.. note::
+  :file:`~/project/html.tar.gz`
+    From CircleCI_ `build-36-docs` Artifacts
 
-   Alternatively, clone into a clean repository.
+  :file:`FiPy-x.y.win32.zip`
+    From AppVeyor_ Artifacts
 
-Build the documentation and the web pages::
+From the :file:`{FiPySource}` directory, unpack :file:`dist/html.tar.gz`
+into file:`documentation/_build` with::
 
-    $ python setup.py bdist_egg
-    $ python setup.py build_docs --pdf --html --cathartic
+    $ tar -xzf dist/html.tar.gz -C documentation/_build
 
 ------
 Upload
@@ -258,7 +256,13 @@ Upload the web site to CTCMS ::
 Update conda-forge feedstock
 ----------------------------
 
-Using a pull request, update the fipy-feedstock_ with:
+Once you push the tag to GitHub_, the fipy-feedstock_ should automatically
+receive a pull request.  Review and amend this pull request as necessary
+and ask the `feedstock maintainers`_ to merge it.
+
+This automated process only runs once an hour, so if you don't wish to wait
+(or it doesn't trigger for some reason), you can manually generate a pull
+request to update the fipy-feedstock_ with:
 
 * revised version number
 * revised sha256 (use ``openssl dgst -sha256 /path/to/fipy-x.y.tar.gz``)
@@ -282,3 +286,4 @@ Make an announcement to `[email protected]`_
 .. _twine: https://pypi.org/project/twine
 .. _fipy-feedstock: https://github.com/conda-forge/fipy-feedstock
 .. _[email protected]: mailto:[email protected]
+.. _feedstock maintainers: https://github.com/conda-forge/fipy-feedstock#feedstock-maintainers