I'm realizing now, that we are at a place with aiki, that filing bugs might not be useful at all.
The story in my mind right now is like a group of us sitting outside of a cool broken down home. Its obvious that the roof is leaking, the windows are smashed, and the door kicked in, or that there never was a driveway for a car. Yet, we keep just sitting out front making comments (aka, filing bugs) about all the problems, complaining about the broken down home. Well, the truth is the plans for the home and even the structure work for that home is salvageable, but we need to actually jump into to action and code fixes. I hope this analogy makes sense. Many many bugs can be wiped out with just new code for aiki. Many bugs, will cease to exist if portions of the code are rethought and rewritten. So, in the push towards 0.9.1 on march 21, I hope that more of us will take to action like roger is doing by committing code. I'm going to try and do my part as well. https://launchpad.net/aikiframework/+milestone/0.9.1 BTW, we have phpunit test setup in the /tests folder in the aiki root if anyone wants to help write unit tests for each major file of Aiki. That would be very helpful to have tests running. There is much that can be done there. Jon -- Jon Phillips 王✳爻气 http://fabricatorz.com ✳ skype: kidproto ✳ irc: rejon +1.415.830.3884 (global) ✳ +86-187-1003-9974 (beijing) _______________________________________________ Mailing list: https://launchpad.net/~aikiframework-devel Post to : [email protected] Unsubscribe : https://launchpad.net/~aikiframework-devel More help : https://help.launchpad.net/ListHelp
