At one point wasn't there talk of bring xwork into the apache fold. Is
that still an option or is that off the table? It seems to me that
since xwork is such a critical piece of struts2 that it should be part
of apache and not opensymphony. Then xwork would be forced to follow
the apache processes.
Ted Husted wrote:
As it stands, XWork is a "stealth" project using a beta/rc release
system.
Working with XWork from Struts is problematic because
* There are no visible mailing lists that track project status
* There are no forums in which to discuss XWork 2 specific issues,
including the release roadmap and the quality of the development build
* Struts 2 is the only major consumer of XWork 2, and our releases are
needed to test XWork in production.
* The beta/rc system will always mandate at least one more Struts
release than a milestone system, since a GA candidate Struts release
must follow a final XWork release.
The simplest resolution would be for XWork to
* utilize its own set of lists and forums and lists, rather than
piggyback on WebWork.
* adopt the milestone release system used by Struts, iBATIS, Tomcat,
HTTPD, MySQL, and many other successful, productive projects.
Using a common milestone system will allow us to test both Struts and
XWork builds in production, and *then* judge the quality by how well
the software performs in the field.
Thoughts?
-Ted.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
