pypiserver

History

PelleK 4b1bd1c9db Refactor test_server to increase speed (#354 ) I gave test_server.py some much needed attention. This file now take ~30 seconds on my machine to run (down from 130 seconds), and I cleaned up the code a little. Let's see how this goes in CI Commits: ------------- * minimize time.sleep, convert to pathlib * refactor, dry code * run black Co-authored-by: Matthew Planchard <mplanchard@users.noreply.github.com>		2020-11-15 15:57:53 -06:00
..
.gitignore	Download `git-new-workdir` for STANDALONE.	2015-09-14 18:47:33 +02:00
README.rst	MAINT: drop standalone, drop py 2.7 and 3.5 (#338 )	2020-10-03 22:25:14 -05:00
bumpver.py	Run black on codebase (#336 )	2020-10-05 21:04:22 -05:00
check_readme.sh	FIX #154 , docs: TC-script checking README RST-compliance for PyPi.	2016-06-28 13:05:11 +02:00
package.sh	Prep for v1.2.1 release	2017-11-29 18:49:27 -06:00
pypiserver-1.2.6-py2.py3-none-any.whl	Updated test & requirements filename	2019-01-31 09:16:54 +01:00
test-docker.sh	Refactor test_server to increase speed (#354 )	2020-11-15 15:57:53 -06:00
test.htpasswd	Updated test & requirements filename	2019-01-31 09:16:54 +01:00

README.rst

====================
Build scripts folder
====================


Files:
======

- ``bumpver.py``             : Bump, commit and tag new project versions
- ``check_readme.sh``        : Check that README has no RsT-syntactic errors.
- ``package.sh``             : Build deployable artifact (wheel) in ``/dist/`` folder.
- ``README.rst``             : This file.


Release check-list:
===================
1. Update ``/CHANGES.rst`` (+ Title + Date) & ``/README.rst`` (Date,
   not version).

2. Push to GitHub to run all TCs once more.

3. Bump version: commit & tag it with ``/bin/bumpver.py``.
   Use ``--help``.
   Read `PEP-440 <https://www.python.org/dev/peps/pep-0440/>`_ to decide the version.

4. Push it in GitHub with ``--follow-tags``.

5. Generate package *wheel* with ``/bin/package.sh``.

6. Upload to PyPi with ``twine upload -s -i <gpg-user> dist/*``

7. Ensure that the new tag is built on hub.docker.com as ``latest`` and as a
   direct tag reference.

8. Copy release notes from ``/CHANGES.rst`` in GitHub as new *"release"* page
   on the new tag.  Check syntactic differences between ``.md`` and ``.rst`` files.