On Tue, 23 Nov 2004 09:30:20 -0800, Martin Cooper wrote: > struts-chain is in struts/sandbox/trunk, yes, and it will likely be > moved into struts/core/trunk as part of Struts 1.3. However, since > we instituted a policy of not depending on any other components > that are unreleased, that's not going to happen until Commons Chain > is released - which is exactly why I'm pushing to get that > released. ;-)
I agree that we should roll a release before changing a dependency. Case in point is rolling 1.2.6 *before* moving to the next release Commons Validator. I also agree that we should roll and release before making a major change to the code base. Case in point is getting a stable 1.2.x line before adding Chain in 1.3.x. Since we are at 1.3.0 (dot-zero), and that Chain is *the* 1.3 feature, I would have no qualms in using a 0.x build from Commons Chain. As a practical matter, I don't think any of us are going to +1 a 1.3.x release until we sort out Commons Chain, so bringing in a pre-GA chain is not going to hold us up. We've released everything else we have checked-in to date, so there is nothing to lose. (As contrast to 1.1, where we started making significant internal changes *before* releasing other code that had been checked-in for months.) In practice, adding a Chain dependency to core it is more likely to help us along, especially now that we are having API discussions regarding Chain. On the Chain thread, I'm going to suggest that we roll a 0.2.0 release of what we have, before considering any API changes. This will also give a JAR that Struts can use now. We could then also look at making changes to the API and compare them to the 0.2.0 Chain "baseline". -Ted. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
