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-03-02 10:50:37 -03:00
parent e4a1fbd67f
commit d093d85615
1 changed files with 11 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
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.
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.