We are trying to get the release process in a better shape, so documenting/improving the xwork release process would be great. Is there any documentation for xwork releases? Feel free to add stuff here:
http://struts.apache.org/2.x/docs/creating-and-signing-a-struts-21x-distribution-new.html I will volunteer for making S2.x releases on a regular fashion, after the docs are complete :) musachy On Sat, Nov 15, 2008 at 9:13 AM, Rainer Hermanns <[EMAIL PROTECTED]>wrote: > Hi, > > xwork 2.0.7 is released and you can kick off the S2.0.14 release process. > > I'd love to get more S2 developers into the XWork development process. > So, are there any S2 (or other interested) developers not yet involved in > XWork who'd like commit access? Please contact me by mail and I'll add > you. > > Regarding current production apps, I'd go with 2.1.X from trunk for > development projects with a target release in 1-3 months and 2.0.14 > (yet to be released) for production ready apps. > I have several projects running based on S2 2.1.X in production use, but > with some patches applied. These patches will soon be added to XWork 2.1.X > and go into the S2 2.1.X codebase. > > As soon as my current project is finished in early December I will have > much more time to work on XWork and S2.1.X again. > > Thanks, > Rainer > > > I totally agree that this is currently a very bad situation. Jeromy's > > tip for static resources is a working fix for the 2.0.12 issue, as well > > as an uprgade to 2.0.13 testing version would be (this was no GA > > release). Please note that we fixed the static resource bug immediately > > when it was reported, and triggered the 2.0.13 build - but since there > > is still the conversion message issue, it will not become GA. > > > > For the needed 2.0.14, we are simply waiting on XWork to be released, > > because the said conversion error problem is not a Struts issue. The bug > > was fixed in XWork code immediately after reporting, but XWork has it's > > own release cycle. That's why it is not in our hand to get out a Struts > > 2.0.14 release candidate, which technically will be nothing more than a > > 2.0.13 with a current XWork build. > > > > I really hope that we will be getting a XWork release this weekend, and > > as soon as it is published, be sure that a 2.0.14 build will pushed out > > right away. And to all those out there using production apps, please > > feel invited to participate on the QA review and voting process for new > > releases with reporting integration test results, because that helps us > > to hunt down the real world issues before we consider a build GA. > > > > - René > > > > Jeromy Evans schrieb: > >> Koen Serry wrote: > >>> * 2.0.12: yes great GA, ah no it doesn't do static resources, so all > >>> client > >>> side validations won't work.... > >>> > >> > >> Just a tip, if you're releasing a production app, you shouldn't be > >> serving static resources from the struts2 dispatcher. Extract them and > >> the problem is avoided. > >> > >> http://struts.apache.org/2.0.12/docs/performance-tuning.html > >> > http://cwiki.apache.org/S2WIKI/creating-a-custom-dojo-profile-for-struts-20x.html > >> > >> > >> > >> > >> --------------------------------------------------------------------- > >> 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] > > > > > > > -- > Rainer Hermanns > aixcept > Willibrordstraße 82 > 52134 Herzogenrath - Germany > w: http://aixcept.de/ > t: +49 - 2406 - 979 22 11 > f: +49 - 2406 - 979 22 13 > m: +49 - 170 - 343 29 12 > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- "Hey you! Would you help me to carry the stone?" Pink Floyd
