We really should be making releases every few weeks anyway. So, we can roll a release now and again when the new dependencies become availability.
I'm very much opposed to making sweeping dependency changes *before* releasing what we already have. Been there, done that, didn't like it, and affirmed it wouldn't happen again. :) -Ted. On Sun, 06 Jun 2004 20:58:18 +0100, robert burrell donkin wrote: > hi ted > > > i'd strongly advise waiting until commons-logging and commons- > beanutils have been released. beanutils in particular removes the > dependency on collections and so allows either incompatible version > of commons-collections to be used. if validator is rolled first > then users will have not be able to use one of the two incompatible > versions of the library. > > waiting until after the new beanutils release would allow validator > and struts to remove their dependencies on commons-collections. it > won't be long (one or two weeks only) before the releases have been > cut so i'd say that it's well worth the wait. > > - robert > > > On 6 Jun 2004, at 13:30, Ted Husted wrote: > > >> My schedule has stabilized again, and I can roll a release of >> Commons-Validator tomorrow night. >> >> There are a few outstanding issues, but they all seem to have >> fixes I can apply. >> >> Thought, technically, I should get myself voted onto the Commons- >> Validator team first :) >> >> -Ted. >> >> >> On Fri, 04 Jun 2004 17:44:55 -0500, Joe Germuska wrote: >> >>> Struts 1.2.1 is blocked on the full release of its commons- >>> validator dependency (1.1.3). Of the open bugs, by my >>> assessment, only a one looks like a showstopper that should be >>> resolved before a release: >>> >>> http://issues.apache.org/bugzilla/show_bug.cgi?id=29004 >>> >>> >>> I reclassified some others that I definitely didn't think >>> classified as blockers; If you're interested in helping, you >>> could look at the rest and see if you can fix them (it's fine >>> to fix non- blocker bugs, of course) or help confirm them or >>> otherwise clarify the issues. >>> >>> I think commons-validator is just blocking on someone having >>> time to be the release manager. >>> >>> Joe >>> >>> >>> At 3:48 PM -0500 6/4/04, [EMAIL PROTECTED] wrote: >>> >>> >>>> Hi >>>> >>>> >>>> I know people has been asking about this before, but I saw >>>> previous posts mention >>>> commons collection 3.0 as a show stopper before the 1.2.1 >>>> release? Isn't 3.0 out already? >>>> >>>> In any case, was just wondering what's in the way of a 1.2.1 >>>> release. >>>> >>>> >>>> I saw that log4j Wiki has a todo list page that lists >>>> remaining items for next release. >>>> Thought that was a good idea. Would also make it easier for >>>> people(me) to see if there was anything >>>> they(I) could do to help( unit test, regression test, >>>> documentation, etc..). >>>> >>>> thx, >>>> Henrik Bentel >> >> >> ------------------------------------------------------------------ >> --- 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]
