Part of the message was lost on the way. Here is (hopefully) the complete one.
I am concerned that the next version of WebWork (or XWork) will be built in a sandbox mode. I hope the sandbox is just a place to try things and design stuff. When features and ideas are stable enough they should be brought into the actual code base in a 'refactor the code' way. WebWork's code has been exercised for quite a while. Therefore, it can be considered mature and probably contains a low number of bugs and should be the base IMHO to move forward. While I am at it and decided to post to WebWork's mailing list, here are some opinions. WebWork's name should remain WebWork for two main reasons IMO. Primarily because it is a framework to build WEB APPLICATIONS. It just happens to be generic enough so that people building WEB APPLICATIONS using WebWork can use it also to extend their application (message driven commands, other types of client, ...) and may be reuse some code. The second reason is that WebWork's name starts to be recognized. I really hope to soon seen release plans with concrete features. 1.4 and may be 1.5 could include bug fixes and small features that do not break backward compatibility. Then 2.0 could include larger feature and some that breaks backward compatibility (but please provide a clear migration path or even better a migration tool). Guys, please use Jira, it is a much better tool to plan releases and move forward than some of the pointless discussions that occured lately on the mailing list. just my 2c ------------------------------------------------------- This SF.NET email is sponsored by: Take your first step towards giving your online business a competitive advantage. Test-drive a Thawte SSL certificate - our easy online guide will show you how. Click here to get started: http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0027en _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
