+1 to all that. Do we need / want to get the docs divided out into the subprojects before we do 1.3.0, or are people happy enough to leave them all dumped in 'core' for now?
I think it would be better to cut 1.3.0 and know the docs need work than to wait, unless someone is ready to swing into action on the docs. I don't think anyone really expects 1.3.0 to be the first GA release, and I don't think that's anything to be ashamed of.
> I can't think of anything we really wanted to (or need to) get donethat is blocking a release,
There is one blocker right now: We need Commons Chain 1.1 released. At one point (on the commons-dev list) Craig had said he'd take a look through and see if he was happy enough with what's there now that we could release it, but I don't believe we heard back. I can probably roll a release of that this weekend, if people think the code base is in good enough shape. Maybe I'll ping the commons-dev list again...
If I recall, this is more a nice-to-have than a requirement, although if we want to hold 1.3.0 until that happens, that's OK. Certainly Struts 1.3 works with Chain 1.0.
I wrote earlier...
> although now that I go looking, it seems> the deal?as though the tiles version of chain-config.xml has disappeared! I have a copy in an old SVN checkout from before I started using the "current" virtual directory, but I don't see any signs of it now and SVN is giving me errors when I try to research its history -- what's
Anyone have answers for this?
Joe
--
Joe Germuska [EMAIL PROTECTED] http://blog.germuska.com "Narrow minds are weapons made for mass destruction" -The Ex
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
