--- Martin Cooper <[EMAIL PROTECTED]> wrote: > On Fri, 20 Feb 2004, Ted Husted wrote: > > > Assuming it was all right with everyone, I'm setting the freeze date > for 1.2.0 for tomorrow (Saturday) night. > > > > I'm updating the release plan. There are still a lot of enhancement > patches that we haven't applied, but I think those can wait for later in > the 1.2.x series. I do intend to start marching down that list and > either accepting or declining whatever patches people have submitted. > So, I'm commenting out that section for the purpose of this release. > > > > All the other criteria have been met, and I believe we are ready to > go. > > > > Martin, would you be able to take it from there, or is there any thing > else I can do? > > Just a few things: > > * What about the new Apache license? Technically, it doesn't need to > change if we release before March 1st, but we're mighty close to that, > so > perhaps we should switch now?
+1 > > * There was a brief discussion not too long ago about whether we should > be > building this release against released versions of Commons components or > the nighlies. Since, in theory at least, this release could be promoted > to > a Final release, I assume the former? At this point I don't see any reason to ever build against commons nightlies unless we're using some unreleased feature. IMO, Struts shouldn't use unreleased commons features because we'll end up in a 1.1 situation where we're waiting for commons releases. The exception would be for alpha releases like Validator where it only needs testing before getting a GA label. > Several of the Commons components > we > depend on have released since we last did, so we may want to update the > versions in our dependency list. Collections is a particularly ugly situation. Do we upgrade to 3.0 and break existing Struts apps requiring 2.x? Or, do we stay at 2.x and break apps needing 3.0? David > > * The Cactus tests won't run for me, for some reason. When I start the > tests, everything looks fine as it starts up, but then it just sits > there > doing nothing. They used to work, but I can't recall what I might have > changed to break it. Anyone have any ideas? Obviously, I don't want to > create a release and not be able to run the tests! > > -- > Martin Cooper > > > > > > -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] > __________________________________ Do you Yahoo!? Yahoo! Mail SpamGuard - Read only the mail you want. http://antispam.yahoo.com/tools --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]