testtools-dev team mailing list archive
-
testtools-dev team
-
Mailing list archive
-
Message #00961
Re: next release time?
On Wed, Jan 25, 2012 at 9:14 PM, Robert Collins
<robertc@xxxxxxxxxxxxxxxxx> wrote:
> We have three unfixed criticals:
> Critical
> Triaged
> #872906 python -m testtools.run discover -v doesn't set verbosity
> testtools Assignee: None Tags: None 0 out of 4 heat flames
>
> Critical
> Triaged
> #881052 assertRaises gives error about a lambda
> testtools Assignee: None Tags: regression 1 out of 4 heat flames
>
I want to block on this one. Error messages from failing tests are
extremely important, and I don't want us going out the door with
(another?) release that gets this one wrong.
I'll try to get around to fixing this tomorrow (UK).
Thanks for the prompt! It has been too long since we released.
jml
References