Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 0 additions & 1 deletion Makefile
Original file line number Diff line number Diff line change
Expand Up @@ -24,7 +24,6 @@ release:
hatchling build
twine upload dist/testtools-$(shell hatchling version)-*
gpg -a --detach-sign dist/testtools-$(shell hatchling version).tar.gz
$(PYTHON) scripts/_lp_release.py

snapshot: prerelease
hatchling build
Expand Down
8 changes: 8 additions & 0 deletions NEWS
Original file line number Diff line number Diff line change
Expand Up @@ -3,6 +3,14 @@ testtools NEWS

Changes and improvements to testtools_, grouped by release.

2.8.2
~~~~~

Changes
-------

Fully migrate away from Launchpad to GitHub.

2.8.1
~~~~~

Expand Down
11 changes: 2 additions & 9 deletions README.rst
Original file line number Diff line number Diff line change
Expand Up @@ -51,24 +51,17 @@ If you would like to use our Twisted support, then you will need the
``testtools[twisted]`` extra.

If you want to use ``fixtures`` then you can either install fixtures (e.g. from
https://launchpad.net/python-fixtures or https://pypi.python.org/pypi/fixtures)
https://github.com/testing-cabalfixtures or https://pypi.python.org/pypi/fixtures)
or alternatively just make sure your fixture objects obey the same protocol.


Bug reports and patches
-----------------------

Please report bugs using Launchpad at <https://bugs.launchpad.net/testtools>.
Please report bugs using GitHub at <https://github.com/testing-cabal/testtools>.
Patches should be submitted as GitHub pull requests, or mailed to the authors.
See ``doc/hacking.rst`` for more details.

There's no mailing list for this project yet, however the testing-in-python
mailing list may be a useful resource:

* Address: [email protected]
* Subscription link: http://lists.idyll.org/listinfo/testing-in-python


History
-------

Expand Down
1 change: 0 additions & 1 deletion disperse.conf
Original file line number Diff line number Diff line change
@@ -1,4 +1,3 @@
# See https://github.com/jelmer/disperse
timeout_days: 5
tag_name: "$VERSION"
launchpad_project: "testtools"
2 changes: 1 addition & 1 deletion doc/for-test-authors.rst
Original file line number Diff line number Diff line change
Expand Up @@ -1422,7 +1422,7 @@ The solution is to use ``Nullary`` instead::
Here, ``repr(nullary)`` will be the same as ``repr(f)``.


.. _testrepository: https://launchpad.net/testrepository
.. _testrepository: https://github.com/testing-cabal/testrepository
.. _Trial: http://twistedmatrix.com/documents/current/core/howto/testing.html
.. _nose: http://somethingaboutorange.com/mrl/projects/nose/
.. _zope.testrunner: http://pypi.python.org/pypi/zope.testrunner/
Expand Down
22 changes: 2 additions & 20 deletions doc/hacking.rst
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ Contributing to testtools
Bugs and patches
----------------

`File bugs <https://bugs.launchpad.net/testtools/+filebug>` on Launchpad, and
`File bugs <https://github.com/testing-cabal/testtools/issues/new>` on GitHub, and
`send patches <https://github.com/testing-cabal/testtools/>` on GitHub.


Expand Down Expand Up @@ -80,12 +80,6 @@ good idea. For crasher bugs, this is generally a no-brainer, but for UI bugs
& API tweaks, the reason something is an improvement might not be obvious, so
it's worth spelling out.

If you are thinking of implementing a new feature, you might want to have that
discussion on the [mailing list]([email protected]) before the
patch goes up for review. This is not at all mandatory, but getting feedback
early can help avoid dead ends.


Documentation
-------------

Expand Down Expand Up @@ -178,10 +172,6 @@ Membership in the testing-cabal org on GitHub as committer.

Membership in the pypi testtools project as maintainer.

Membership in the https://launchpad.net/~testtools-committers.

No in-progress Critical bugs on the next_ milestone.

Tasks
+++++

Expand All @@ -190,19 +180,11 @@ Tasks
#. Possibly write a blurb into NEWS.
#. Commit the changes.
#. Tag the release, ``git tag -s X.Y.Z -m "Releasing X.Y.Z"``
#. Run 'make release', this:
#. Creates a source distribution and uploads to PyPI
#. Ensures all Fix Committed bugs are in the release milestone
#. Makes a release on Launchpad and uploads the tarball
#. Marks all the Fix Committed bugs as Fix Released
#. Creates a new milestone
#. If a new series has been created (e.g. 0.10.0), make the series on Launchpad.
#. Push trunk to GitHub, ``git push --tags origin master``
#. Push master to GitHub, ``git push --tags origin master``

.. _PEP 8: http://www.python.org/dev/peps/pep-0008/
.. _unittest: http://docs.python.org/library/unittest.html
.. _MIT license: http://www.opensource.org/licenses/mit-license.php
.. _Sphinx: http://sphinx.pocoo.org/
.. _restructuredtext: http://docutils.sourceforge.net/rst.html
.. _testing-cabal: https://github.com/organizations/testing-cabal/
.. _next: https://launchpad.net/testtools/+milestone/next
235 changes: 0 additions & 235 deletions scripts/_lp_release.py

This file was deleted.