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