From d093d85615c4921bbb25fe95c889634318e6a93a Mon Sep 17 00:00:00 2001 From: "Rolando (Max) Espinoza" Date: Thu, 2 Mar 2017 10:50:37 -0300 Subject: [PATCH] Updated Scrapy release procedure (markdown) --- Scrapy-release-procedure.md | 13 +++++++++++-- 1 file changed, 11 insertions(+), 2 deletions(-) diff --git a/Scrapy-release-procedure.md b/Scrapy-release-procedure.md index bd67a8f..fdb8a05 100644 --- a/Scrapy-release-procedure.md +++ b/Scrapy-release-procedure.md @@ -97,6 +97,15 @@ $ git push origin master 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. -See the release update checklist: https://github.com/conda-forge/scrapy-feedstock#updating-scrapy-feedstock +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. -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 +Checklist for new releases: + +1. Update the ``version`` string. +2. Update the ``sha256sum`` from the PyPI's [source release + tarball](https://pypi.org/project/Scrapy/#files). +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 requirements declared in ``setup.py``. +5. Do a test build locally to ensure everything is OK. +6. Create a branch in your own fork and submit the PR. \ No newline at end of file