KUROSAKA Teruhiko wrote:
Ted,
I'm now testing, tagging, and rolling Struts 1.2.1. Please stand by :)
As far as I can tell by monitoring this list, 1.2.1 seems to fix only face related few bugs. It didn't pick most patches available in bugzilla.
If by "face" you mean JavaServer Faces, it doesn't actually include *any* of those changes ... the Struts-Faces integration library is not a part of the core release, and will be released separately when it's done. That being said, there have been a very large number of changes (both enhancements and bug fixes) to Struts since 1.1 was released (over a year ago). A brief summary of those changes can be found in the release notes document (grab the nightly build, install the struts-documentation webapp, and navigate to page "userGuide/release-notes.html"). Yet, few people are benefitting from those changes because they are hesitant to rely on "unreleased" software.
So, our primary mission at this point is to get one stable release out the door in the 1.2.x chain, so that users can get the benefits of all those improvements. After that occurs, I for one will certainly feel less hesitant about applying patches provided in Bugzilla reports -- especially those that have unit test additions to, so we can avoid future regressions in the areas being corrected.
Could you tell comitters pick patches for the next release? Only by a chance?
I'm not complaining. I just want to know what else I can do to make sure my patch will be picked next time.
Regards,
Craig
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
