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?
How do we relate the contrib packages to the release? Do we consider them part of the release? When I made a change to the Javascript tag class, and dealt with the struts-el ripples, I found that at the time, the EL tests weren't building against the nightly build because they imported ApplicationConfig, which has been removed. I fixed that, but it made me wonder about this general question.
I don't want to hold things up at all, but I'm wondering if we want to do at least a little checking of contrib packages against official Struts releases? We could set this as a future goal to avoid delaying 1.2.0, and maybe it's not even a goal -- but I thought I'd ask.
Joe
--
Joe Germuska [EMAIL PROTECTED] http://blog.germuska.com "Imagine if every Thursday your shoes exploded if you tied them the usual way. This happens to us all the time with computers, and nobody thinks of complaining."
-- Jef Raskin
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
