I'm working my way through the issue lists, trying to hit low hanging fruit, and get rid of duplicates and other things.
I'm resolving many issues as "won't fix", not because they are invalid, but because the problems described are small, or the fix is highly disruptive, or because the committer team simply doesn't have the bandwidth to address the problem. In some cases, re-opening the issue and supplying a patch (with tests!) can change the disposition of the issue. I'm very interested in getting 5.4 out the door; there's still a number of serious issues barring the way, and the backlog of bugs is proving to be a real impediment. -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com @hlship
