[Distutils] Distribute 0.6.7 this week

[Tarek Ziadé]

On Tue, Oct 27, 2009 at 3:12 PM, ssteinerX at gmail.com
<ssteinerx at gmail.com> wrote:
>
> On Oct 27, 2009, at 4:53 AM, Tarek Ziadé wrote:
>
>> Hello
>>
>> We are going to release 0.6.7 this week. Among some new bugs fixes, we
>> want to provide a specific change that will
>> allow virtualenv to be released with an option to use Distribute
>> instead of Setuptools, like zc.buildout.
>>
>> $ virtualenv --distribute ENV
>>
>> If you want to see another bug fixed in this release,  speak up !
>> (http://bitbucket.org/tarek/distribute/issues)
>
> I don't necessarily have a request bug-wise, but maybe this would be a good
> time to coordinate the upgrading of the test suite with the release.
>
> Maybe something like a TEST_README documenting the tests that prove the that
> the closed ticket's bugs have a test that proves that the former bad
> behaviour was fixed.

Maybe a simpler way would be to use Bitbucket issue tracker features ?

For the last two bugs I've fixed, they have a corresponding test in the commit.
And if you go to the issue, you have a link to the commit with a diff,
so you can see it.

That's done with the special "fixes #N" bit in the commit messages,
where N is the issue number.
Bitbuckets links the tyicket with the commits when its pushed there.

So we could maybe add the link to the issue in CHANGES ?

Although some parts are cleary undertested yet, so even if it's
unpleasant to add tests
in an undertested code base, I am +1 in making the tests mandatory
when the code is not yet covered
for now on

Tarek