I've been through Apps, and it's looking quite good now. There were only very minor fixes to the pages, everything seems to be working well.
Many thanks to Wendy and James and everyone who's been working on the Maven builds. It's all come together very nicely. IMHO, the process is more accessible, and it will be much easier for people to get involved in the project, or get involved again after being away for a while. As to remaining steps, I think all we need to do is (1) Make a final pass on the documentation and configuration files, to be sure all is current with the release plan. (2) Rename struts-core as struts-action. (3) Finalize what we are going to do with #36794 - the CG lib DynaForm enhancements. (4) Final updates the release notes as to recent changes. (5) Set 1.3.0 tags for each subproject (ACTION_1_3_0, APPS_1_3_0, EL_1_3_0, ...) . (6) Assembly a ZIP archive of the respective JARs as the "Struts Action Framework Library". (7) Post for review As to (3), one option is to move the code to the Extras subproject. We might also want to consider if we want to move some other optional classes there too. One candidate might be [org.apache.struts.validator.ValidatorActionForm], which is the "path" attribute version of ValidatorForm. Release caveats are that we have two dependencies on non-GA code: Commons Validator and Commons Resources. Commons Resources is being used as part of the Extras subproject. All I did was build the dev code from a nighly buid and post the JAR in the Apache repository. Is anyone up for a Commons Resources release? These caveats would keep a 1.3.0 release of Action Framework and Extras from going GA, but I think we anticipate additional changes anyway, so I don't see that they should keep us from rolling it. -Ted. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
