pypiserver

History

Matthew Planchard 972f1616dd Use GitLab as CI Provider (#269 ) * Add gitlab CI * minmor updates to readme in /bin * no autodeploy; less scary		2019-09-17 20:44:15 -05:00
..
.gitignore	Download `git-new-workdir` for STANDALONE.	2015-09-14 18:47:33 +02:00
bumpver.py	REL: Prep for v1.2.2	2018-06-12 19:58:31 -05:00
check_readme.sh	FIX #154 , docs: TC-script checking README RST-compliance for PyPi.	2016-06-28 13:05:11 +02:00
commit-standalone.sh	fix(standalone): `.standalone` dir were already created by git-workdir	2017-12-03 12:07:59 +02:00
gen-standalone.sh	FIX: Fallback URL, remove calls to pip.main	2018-06-11 20:31:03 -05: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
README.rst	Use GitLab as CI Provider (#269 )	2019-09-17 20:44:15 -05:00
test_standalone.sh	* added debug flags to bash scripts	2016-07-17 15:23:20 -05:00
test-docker.sh	Use GitLab as CI Provider (#269 )	2019-09-17 20:44:15 -05: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.
- ``commit-standalone.sh``   : Create an executable file and add it into `standalone` branch.
- ``gen-standalone.sh``      : Invoked by `commit-standalone.sh`.
- ``git-new-workdir``        : Invoked by `gen-standalone.sh`.
- ``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. Run ``bin/commit-standalone.sh``.

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.