From 8da949acb4996479e42a5d5a6c78d731fb1d7ff2 Mon Sep 17 00:00:00 2001 From: "Rolando (Max) Espinoza" Date: Mon, 13 Feb 2017 14:36:56 -0400 Subject: [PATCH] Updated Scrapy release procedure (markdown) --- Scrapy-release-procedure.md | 18 +++++++++++++++++- 1 file changed, 17 insertions(+), 1 deletion(-) diff --git a/Scrapy-release-procedure.md b/Scrapy-release-procedure.md index be7ab88..898e4d7 100644 --- a/Scrapy-release-procedure.md +++ b/Scrapy-release-procedure.md @@ -90,4 +90,20 @@ $ git push origin 1.0 --tags $ git checkout master $ git cherry-pick 1.0 # resolve any conflicts on docs/news.rst $ git push origin master -``` \ No newline at end of file +``` + +## Conda packages + +The recipe is located here: https://github.com/conda-forge/scrapy-feedstock/tree/master/recipe +The procedure is through PRs from a fork against the master branch. + +Checklist: + +1. Update the ``version`` string. +2. Update the ``sha256sum`` of the release tarball. This can be done by downloading the tarball from pypi and compute the sha256sum. +3. Reset the ``build.number`` to ``0``. This number is only increased when we re-build a package with no version change. +4. Update requirements if needed. This can be done by checking the ``setup.py`` changes between releases. +5. Do a test build locally to ensure everything is OK. +6. Create a branch in your fork and submit the PR. + +The PR will trigger builds in Travis CI, Circle CI and Appveyor. This may take a while depending on the conda-forge build queue. Once builds are OK, the PR is ready to merge and packages will be uploaded to the `conda-forge` channel automatically. \ No newline at end of file