[Windmill-dev] Windmill 0.2 Status

Mikeal Rogers mikeal at osafoundation.org
Fri Aug 24 15:34:56 PDT 2007


We have 2 milestones for the 0.2 release. 0.2-Beta is our "as soon as  
possible" release which is targeted at getting windmill 0.2 ready for  
tinderbox integration at OSAF. Another 0.2-Release is planned  
afterwards and includes some additional features and general cleanup  
of all the "ruff edged" we've seen people encounter using windmill.

We have one ticket targeted for 0.2-Beta;
http://windmill.osafoundation.org/trac/ticket/27

I haven't gotten the feedback I need from firefox-dev on this yet so  
I'm going to have to punt it to 0.2-Release.

This doesn't mean we're done. Bear and Adam are tracking some yet to  
be logged blockers that are cause tinderbox to hang. Once those are  
logged and marked fixed we can look at tagging and releasing 0.2-Beta.

One important piece of feedback we have right now is that the  
wxPython based UI is a bit too buggy to ship. In addition the people  
who tend to be trying to use it right now are using it because it's  
the first thing they see, then leaving the project out of  
frustration. Not that all of the bugs in windmill are in the wxPython  
UI, we have plenty elsewhere and that's kind of the issue, we some  
bugs everywhere and need to focus.

Adam and I have talked about this and we're thinking of pushing out  
the integration of the wxPython UI in windmill. This includes  
changing the default windmill binary to print the CLI help menu when  
no arguments are passed, de-linking the .app/.exe binaries, and  
changing the build process for pre-built binaries to build without  
wxPython for the CLI only. This also simplifies the documentation  
quite a bit.

We want to focus on stability of our existing functionality and  
integrating important new features rather than splitting our time and  
focus between 3 different run options and integrating each new  
service feature in to the wxPython UI's menu system. The wxPython ui  
isn't going anywhere, it will remain in the code base and the option  
to run it will remain in windmill-admin.py and development will  
continue on it but we won't be supporting it or promoting it until  
all the outstanding issues are fixed.

Thoughts?

-Mikeal

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osafoundation.org/pipermail/windmill-dev/attachments/20070824/48d5a609/attachment.htm


More information about the Windmill-dev mailing list