FWIW, I've just looked through the outstanding bugs for (used the query "project = VALIDATOR AND issuetype = Bug AND status in (Open, "In Progress", Reopened)").
There were 19 issues. I made some comments in JIRA and have categorized them below. Of those, 8 seem to be ready for resolution: https://issues.apache.org/jira/browse/VALIDATOR-288 - Appears to have been fixed as result of https://issues.apache.org/jira/browse/VALIDATOR-248. https://issues.apache.org/jira/browse/VALIDATOR-286 - Appears to have been resolved in snapshot 1.4. https://issues.apache.org/jira/browse/VALIDATOR-278 - Comments indicate fixed in snapshot 1.4 https://issues.apache.org/jira/browse/VALIDATOR-273 - Patch provided - needs to be applied? https://issues.apache.org/jira/browse/VALIDATOR-271 - Comments indicate fixed in snapshot 1.4 https://issues.apache.org/jira/browse/VALIDATOR-264 - Reported against the deprecated EmailValidator. Attempt to recreate failed. https://issues.apache.org/jira/browse/VALIDATOR-259 - Patch provided in bug - needs to be applied? https://issues.apache.org/jira/browse/VALIDATOR-240 - Changes already in snapshot 1.4. Acceptable(?) source now in comments on issue. The following don't seem urgent since they're either optimization issues or reported against pre-1.3.1 versions: https://issues.apache.org/jira/browse/VALIDATOR-266 - Suggested optimization for DomainValidator. https://issues.apache.org/jira/browse/VALIDATOR-261 - Reported against 1.2.0. Request to revert a warning message that was reported against. https://issues.apache.org/jira/browse/VALIDATOR-268 - Reported against 1.1.4 Which leaves only 8 issue of varying complexity. Some are requests for additional support and/or better confirmity to RFCs: https://issues.apache.org/jira/browse/VALIDATOR-276 - The validator seems to require an Authority (which it considers the start of the path name in at least some of the cases) whereas RFC-2396 states that it's optional for some schemes. https://issues.apache.org/jira/browse/VALIDATOR-267 - The bug claims domain comments and other constructs are permitted in RFC2822 https://issues.apache.org/jira/browse/VALIDATOR-235 - Umlaut, etc. in domain names. https://issues.apache.org/jira/browse/VALIDATOR-225 - Localized validation of number formats in javascript https://issues.apache.org/jira/browse/VALIDATOR-207 - There's a suggestion to close as WONTFIX and improve docs. https://issues.apache.org/jira/browse/VALIDATOR-282 - Would likely break existing code. https://issues.apache.org/jira/browse/VALIDATOR-277 - I don't have enough JavaScript expertise to evaluate https://issues.apache.org/jira/browse/VALIDATOR-257 - ditto Aside from the JavaScript-related ones, I'm willing to provide some patches. However, before doing that ... could we get an indication that there is willingness among committers to release a 1.4 version (or a 1.3.2 with just the currently fixed bugs) with a relative priority of the outstanding issues? jz -----Original Message----- From: Niall Pemberton [mailto:niall.pember...@gmail.com] Sent: Tuesday, February 22, 2011 8:28 PM To: Commons Developers List Subject: Re: release commons validator 1.4 On Mon, Feb 21, 2011 at 9:58 PM, David Karlsen <davidkarl...@gmail.com> wrote: > ping? Apologies, I'm very busy at work and don't know if/when I'll get time to do this. Sorry Niall > 2011/1/27 David Karlsen <davidkarl...@gmail.com> > >> Any update to the status? >> >> 2011/1/19 Niall Pemberton <niall.pember...@gmail.com> >> >> On Wed, Jan 19, 2011 at 3:09 PM, Jacob Zwiers >>> <jacob.zwi...@tpsgc-pwgsc.gc.ca> wrote: >>> > I'll echo that. >>> > >>> > I had put a query to the user's list a last week asking a similar >>> question. >>> > >>> > I understand that the committers are working on JSR-303 and >>> > validator2 >>> releases. >>> > >>> > However, I suspect we're not the only ones looking to get get off >>> Jakarta-ORO sooner than later. >>> > >>> > Is there an interest among committers to push a 1.4 release? >>> >>> I will try to find some time to look at doing this. >>> >>> > If so, where do you see volunteer help being most useful? >>> >>> At this point I don't know. I need to review/remember the state >>> validator is currently in and come up with a TODO list for a 1.4 >>> release. >>> >>> Niall >>> >>> > jz >>> > >>> > >>> > -----Original Message----- >>> > From: David Karlsen [mailto:davidkarl...@gmail.com] >>> > Sent: Wednesday, January 19, 2011 9:59 AM >>> > To: dev@commons.apache.org >>> > Subject: release commons validator 1.4 >>> > >>> > Hi. >>> > >>> > We'd be very interested in >>> > >>> http://commons.apache.org/validator/apidocs/org/apache/commons/valid >>> ator/routines/checkdigit/LuhnCheckDigit.html- >>> > could 1.4 be released? >>> > It's been quite a while since the last 1.3.1 relase >>> > >>> > -- >>> > -- >>> > David J. M. Karlsen - http://www.linkedin.com/in/davidkarlsen >>> > >>> > ------------------------------------------------------------------ >>> > --- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >>> > For additional commands, e-mail: dev-h...@commons.apache.org >>> > >>> > >>> >>> -------------------------------------------------------------------- >>> - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >>> For additional commands, e-mail: dev-h...@commons.apache.org >>> >>> >> >> >> -- >> -- >> David J. M. Karlsen - http://www.linkedin.com/in/davidkarlsen >> >> > > > -- > -- > David J. M. Karlsen - http://www.linkedin.com/in/davidkarlsen > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
