If you're a Commons Committer already, just add your name to the roster, and have at it :)
Essentially, make sure that it would be ready for release, and then float a vote to promote it. Once it's promoted, we can roll a release and move the Struts 1.3.x dependencies (if we are ready to declare the HEAD 1.3.x). On Fri, 29 Oct 2004 08:43:52 -0400, James Mitchell wrote: >�I would like to start pushing commons-resource for promotion so we >�can move to it in the 1.3.x time frame. �I have never been part of >�the promotion process, but I am willing to do all the work. �Does >�it make sense for me to start this ball rolling? > > >�-- >�James Mitchell >�Software Engineer / Open Source Evangelist >�EdgeTech, Inc. >�678.910.8017 >�AIM: jmitchtx > >�----- Original Message ----- >�From: "Ted Husted" <[EMAIL PROTECTED]> >�To: <[EMAIL PROTECTED]> >�Sent: Friday, October 29, 2004 8:17 AM >�Subject: Problem Issue Roadmap > > >�I started a Problem Issue Roadmap to prepare for a 1.2.6 milestone, >�but now that we've started to break the MailReader database out >�into a separate package, perhaps we should forge ahead and look >�towards 1.3.0. > >�Are we ready for the 1.3.0 plunge? > >�---- > >�Problem Ticket Roundmap > >�* #5157 - logic:iterate attributes inconsistent with rest of struts >�- Could be invalid > >�* #18169 - Resource attribute of msg tag in the validation.xml >�doesn't work as anticipated - Could be Commons Validator issue > >�* #23127 - Page attribute of img and image tags doesn't use >�pagePattern setting - No patch, but we could try to resolve > >�* #31230 - Multiple classes using deprecated DefinitionsUtil class - >� Patch to DefinitionDispatcherAction could be considered, and the >�rest tabled for 1.3. > >�#31501 - html:form focus generates non-XHTML - Could be invalid > >�#31642 - <bean:include>�always include Session id (if any) even for >�external Urls (href attribute) - Patch could be considered > >�#31658 - LogonAction does not check errors in appropriate place - >�Fix could be considered > >�#31684 - html:frame tag anchor attribute does not appear to pass >�along correctly - More information needed. We might need to add a >�frames page to the examples application. > >�#31827 - Bug in validation part - Could be a support issue > >�---- > >�-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] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
