Bob Harner wrote:
As an aside, this seems to illustrate why it would be much better to base ongoing Lenya development on a *released* version of cocoon and not its trunk, right? If 1.4 is to be released in a few weeks, it would have to be based on Cocoon's most recent release, right? That's 2.1.10. The last I heard was that most Lenya developers are using the Cocoon trunk rather than the 2.1.10 release (is this still the case?), which means that significant extra testing (and patching?) would need to be done before releasing 1.4.
important point. but the 2.1.11 release is imminent, and so we might have a good chance of a sync'ed release.
in general, i prefer following the cocoon trunk during most of the development cycle (continous integration among apache projects does create some friction, but it's generally a Good Thing imho), but i agree that we should "freeze" our cocoon external a lot earlier in future releases, to guarantee proper testing.
after 1.4 is out the door, we should talk about cocoon 2.2 anyways, and iiuc they are considering block-wise releases, which might complicate a few things for us...
regards, jörn --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
