Sylvain Wallez wrote:
Stephen McConnell wrote:
Let me give some details, since I'm currently working on sourceresolve after some discussion with Carsten. We want to reach API stability on this, because it's used in many places in Cocoon and a such is required if we want to start releasing Cocoon 2.1 (we're not even alpha yet).
To answer your questions, the plan is to start by refining and stabilizing the API and document it, and test into Cocoon 2.1. There's no problem if we start by testing with Cocoon before writing automated unit tests because of the unreleased nature of the 2.1 branch.
Detailed docs and automated unit tests will be written in a second phase, and any help in this area is more than welcome !
Also, I don't see a dependency of sourceresolve on pool. Where did you find it (I'm not fully "fluent" with Avalon build system) ?
The only reason I could think of is for testing purposes. SourceResolve currently defers to component handlers....
-- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
