Release testtools to PyPI

[Francis J. Lacoste]

testtools is only available as a branch on Launchpad. This makes it hard to use in third-party application.

Please consider doing a formal release and linking it from PyPI.

[Francis J. Lacoste (flacoste)]

Of course, this will require fixing bug 280874

[Jonathan Lange (jml)]

Good point.

Arguably, it's a bug in Launchpad that having a project hosted only on Launchpad makes it hard to use in third-party apps!

I'm unlikely to do official releases any time soon. Maybe I can have my arm twisted.

[Jonathan Lange (jml)]

To be clearer though, what do you mean by formal release and what observable benefits would it give?

[Francis J. Lacoste (flacoste)]

On June 29, 2009, Jonathan Lange wrote:
> To be clearer though, what do you mean by formal release and what
> observable benefits would it give?

I mean a tar ball with a version number, ideally with proper changelog.

The most immediate benefit is that it means that it would be possible to state
in the setup.py project that requires testtools, to formally list that
dependency.

And also track changes between versions.

You know, usual release management stuff ;-)

--
Francis J. Lacoste
<email address hidden>

[Jonathan Lange (jml)]

On Mon, Jun 29, 2009 at 6:39 PM, Francis J.
Lacoste<email address hidden> wrote:
> On June 29, 2009, Jonathan Lange wrote:
>> To be clearer though, what do you mean by formal release and what
>> observable benefits would it give?
>
> I mean a tar ball with a version number, ideally with proper changelog.
>

If I made a release tarball, it would be a tarball of trunk, the
version number would be the revision number, the changelog would be a
copy of 'bzr log -r7..' -- why would I do anything more?

> You know, usual release management stuff ;-)

Bah. 'Usual stuff' is for people with copious spare time. I'm
constantly improving my processes by looking beyond 'best practice' :P

jml