dusty wrote:
How do we tackle all this? Do we have a meeting? Do we create a Chief who can make decisions for better or for worse? Clearly decisions need to be made. Do we start StrutsCon 2009 and lock everyone in a room until the decisions are made? I started to also write apps in Rails and I promised myself I would learn Grails to stay current, but judging from Phillip's session at JavaOne and the traffic on the mailing list there is still A LOT of interest in S2. Ideas? Volunteers? Beueller?
I share similar sentiment. Whenever I take a critical look as to whether to use struts2 I keep coming back to the conclusion that it's fundamentally sound as far as java frameworks go. I'd categorize the problem as not enough generals. Most of us can make incremental improvements or start new plugins but few have the courage to to drive through fundamental changes or remove features. I'd join some kind of coordinated hack-a-thon to break through the inertia.
My #1 issue is that it's *too difficult and time-consuming to create a release* on the 2.1 trunk. If releases are difficult and dependent on a few key individuals then momentum slows and the project inevitably stalls.
I've been independently tinkering with release process to try to automate all assembly within a CI system so a formal release is an administrative process only, but it's not much fun.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
