Status report

It seems that my attempt at rallying the troops failed a bit... :}

Samuele did some testing (and even added a new test -- great!), but
apart from that it seems that the people I suggested for testing were
too busy or something. Fair enough.

(Thomas Heller did respond. Thomas: Thanks for the heads up! :)

Anyway, I'm in the process of installing the back-end toolkits I don't
already have (I just got PyQt nailed down; I'll try to get PyGTK
working in Windows next) so I can do whatever testing/debugging is
necessary myself. All in all it seems like things are in pretty good
shape, so getting the alpha out by the end of the month should be a
definite possibility, I think. I won't be able to test beosgui, but
from what I understand it is quite broken anyway, and probably won't
be a part of 0.2a0.

If someone (Joe?) could test textgui and cursesgui I would appreciate
it -- I don't really remember the details of how to use them :]

Any voluntary effort elsewhere would also be appreciated, of course;
if anyone wants to contribute but needs some hints of where to begin,
just say so. I'm sure we can think of something :)

And another thing... (Will he ever stop? ;) I think we should start
using a proper bug tracker (i.e. the SourceForge bug tracker). Does
anyone have any experiences with it?

-- 
Magnus Lie Hetland        Practical Python          The Anygui Project
http://hetland.org        http://ppython.com        http://anygui.org


-------------------------------------------------------
This sf.net email is sponsored by: Influence the future 
of Java(TM) technology. Join the Java Community 
Process(SM) (JCP(SM)) program now. 
http://ad.doubleclick.net/clk;4729346;7592162;s?http://www.sun.com/javavote