@@ -72,9 +72,6 @@ If you're used to open-source Python development with Git, here's the gist:
7272.. _the bug tracker : https://github.com/python-ldap/python-ldap/issues
7373.. _tox : https://tox.readthedocs.io/en/latest/
7474
75- Or, if you prefer to avoid closed-source services:
76-
77- * ``git clone https://pagure.io/python-ldap ``
7875* Send bug reports and patches to the mailing list.
7976* Run tests with `tox `_; ignore Python interpreters you don't have locally.
8077* Read the documentation directly at `Read the Docs `_.
@@ -203,8 +200,6 @@ remember:
203200 * Consider making the summary line suitable for the CHANGES document,
204201 and starting it with a prefix like ``Lib: `` or ``Tests: ``.
205202
206- * Push to Pagure as well.
207-
208203If you have good reason to break the “rules”, go ahead and break them,
209204but mention why.
210205
@@ -224,7 +219,7 @@ If you are tasked with releasing python-ldap, remember to:
224219* Run ``python setup.py sdist ``, and smoke-test the resulting package
225220 (install in a clean virtual environment, import ``ldap ``).
226221* Create GPG-signed Git tag: ``git tag -s python-ldap-{version} ``.
227- Push it to GitHub and Pagure .
222+ Push it to GitHub.
228223* Release the ``sdist `` on PyPI.
229224* Announce the release on the mailing list.
230225 Mention the Git hash.
0 commit comments