So, my question was, why do they think the code isn't good enough for a release? Now it seems that Struts 1.1 is ready, some other component isn't ready. If that's the case, can that component be removed, then added in a 1.2 release? If it's another jar, it's extremely simple to add a jar when it's ready.
We do think it's good enough to release. That's why we dubbed the last beta a Release Candidate.
Unfortunately, we can't just drop a components, since the components compose the API, and many existing applications would not work. The JARs are needed at runtime, and if you can't use an unreleased Struts JAR, then you couldn't use an unreleased Commons JAR either. Basing our release on other unreleased components isn't going to help you.
If we were truly desperate, we could import the remaining packages into our own CVS and release them that way. But, being volunteers, we're not up for that kind of pain.
Meanwhile, most of the Struts committers are using the Release Candidate in production. We do trust it in our own companies.
-Ted.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
