On Tue, Sep 18, 2012 at 6:54 PM, Alexander Shorin <kxe...
>> - The default branch in general is. What would it take to get an
>> 0.8.1 or 0.9.0 ready? What's changed since 0.8?
> Since there was major changes in http module, cjson deprecation and
> support all design functions, it couldn't count for revision release
> imho. Full changes easy to view via hg log -r 0.8:tip
Would it be possible to get an 0.9 milestone, and have issues assigned
to it? For example, it seems like this has been fixed already:
I'd be willing to wade in and work on the organization, but I
recognize that I probably haven't earned the trust that being imbued
with that kind of authority / responsibility would require.
>> - What state the tests are in. Can someone wanting to contribute rely
>> on the current set of tests to provide adequate coverage?
> Some things currently are not test friendly (like http module). Some
> things are not well testable like:
> since I dont know any good methods to emulate race conditions without
> massive threading usage and patching internals. May be you know?
While it probably doesn't make sense to have it as a unit test, I
think that massive threading, etc. is fine to have as a test script
that can be run to provoke the problem (and then be run and not
provoke after the fix is in).
I think that some clear direction from the owners would be helpful. I
would suggest that it might make sense to split the issue into two;
one for fixing the immediate problem, and one for addressing the
>> - I recall there being some changes to session handling from 0.8; is
>> that work done, or was more planned?
> Since everything works, looks that session changes are complete.
Heh, I was more meaning "is there another phase of refactoring yet to come."