RELEASE.rst: move conda preparation further down

RELEASE.rst

@@ -122,38 +122,6 @@ Then create a zipped version of the HTML documentation and name the PDF consiste
     mv docs/build/latex/kwant.pdf docs/build/kwant-doc-<version>.pdf
 
 
-Clone the repository of the Kwant conda-forge package
------------------------------------------------------
-
-This step needs to be performed only once.  The cloned repository can be reused
-for subsequent releases.
-
-Clone the "Kwant feedstock" repository and go into its root directory.  If you
-keep the Kwant source in "src/kwant", a good location for the Conda package
-repository is "src/conda-forge/kwant"::
-
-    cd ~/src
-    mkdir conda-forge
-    cd conda-forge
-    git clone https://github.com/conda-forge/kwant-feedstock kwant
-    cd kwant
-
-Rename the default remote to ``upstream``::
-
-    git remote rename origin upstream
-
-Create a new version of the Kwant conda-forge package
------------------------------------------------------
-
-Edit the file ``recipe/meta.yml``. Correctly set the ``version``
-at the top of the file to the version of this release. Set the ``sha256``
-string in the ``source`` section near the top of the file to the SHA256 hash
-of the kwant source tarball that we previously created. You can find the
-SHA256 hash by running ``openssl sha256 <filename>`` on Linux and Mac OSX.
-
-Commit your changes.
-
-
 Clone the repository of the Kwant Debian package
 ------------------------------------------------
 
@@ -309,6 +277,7 @@ Another example: build source package only::
 
     gbp buildpackage --git-export-dir=/tmp -S
 
+
 Build backports for the current Debian stable
 ---------------------------------------------
 
@@ -326,6 +295,7 @@ Build backported packages::
 
 Do not commit anything.
 
+
 Publish the release
 ###################
 
@@ -333,6 +303,7 @@ If the Debian packages build correctly that means that all tests pass both on
 i386 and amd64, and that no undeclared dependencies are needed.  We can be
 reasonably sure that the release is ready to be published.
 
+
 git
 ---
 
@@ -340,6 +311,7 @@ Push the tag to the official Kwant repository::
 
     git push origin v<version>
 
+
 PyPI
 ----
 
@@ -354,6 +326,7 @@ not only the contents) as the one used for the Debian packaging.  Otherwise it
 will not be possible to build the Debian package based on the tarball from
 PyPI.
 
+
 Kwant website
 -------------
 
@@ -363,6 +336,7 @@ uploaded to the downloads section of the website::
 
     scp dist/kwant-<version>.tar.gz* kwant-project.org:webapps/downloads/kwant
 
+
 Debian packages
 ---------------
 
@@ -419,6 +393,7 @@ Once all the packages have been added, upload the repository::
 
     rsync -avz --delete dists pool kwant-project.org:webapps/downloads/debian
 
+
 Ubuntu packages
 ---------------
 
@@ -471,6 +446,39 @@ Now the changes files are "put" to start the build process on the PPA servers::
     dput ubuntu-ppa-kwant *~*.changes
 
 
+Clone the repository of the Kwant conda-forge package
+-----------------------------------------------------
+
+This step needs to be performed only once.  The cloned repository can be reused
+for subsequent releases.
+
+Clone the "Kwant feedstock" repository and go into its root directory.  If you
+keep the Kwant source in "src/kwant", a good location for the Conda package
+repository is "src/conda-forge/kwant"::
+
+    cd ~/src
+    mkdir conda-forge
+    cd conda-forge
+    git clone https://github.com/conda-forge/kwant-feedstock kwant
+    cd kwant
+
+Rename the default remote to ``upstream``::
+
+    git remote rename origin upstream
+
+
+Create a new version of the Kwant conda-forge package
+-----------------------------------------------------
+
+Edit the file ``recipe/meta.yml``. Correctly set the ``version``
+at the top of the file to the version of this release. Set the ``sha256``
+string in the ``source`` section near the top of the file to the SHA256 hash
+of the kwant source tarball that we previously created. You can find the
+SHA256 hash by running ``openssl sha256 <filename>`` on Linux and Mac OSX.
+
+Commit your changes.
+
+
 Conda forge
 -----------
 This step requires a GitHub account, as Conda forge packages are autobuilt