RomanNum3ral
/
scrapy
mirror of https://github.com/scrapy/scrapy.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Updated Scrapy release procedure (markdown)

Rolando (Max) Espinoza 2017-02-13 14:36:56 -04:00
parent 74153e5be3
commit 8da949acb4
1 changed files with 17 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
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
```
```
## 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.