On Tue, Aug 19, 2014 at 5:28 AM, Nick Wellnhofer <[email protected]> wrote:
> I could imagine that the release schedules of Lucy and Clownfish will > diverge at some point. Maybe we should also try to keep the Lucy master > branch compatible with an official Clownfish release. Then Lucy would only > be updated for Clownfish changes once a new version of Clownfish is > released. This would essentially force us to release Lucy and Clownfish > separately. In the long term, divergence is inevitable. > On the other hand, it might be useful to test whether changes to Clownfish > work with Lucy as soon as possible. Clownfish is likely to remain in significant flux at least until we've implemented bindings for more languages. Here are some of the upcoming challenges which will likely require modifications to the Clownfish core: * Tracing GC (Ruby, Go) * Ordering requirements for optional parameters (Python) * Non-UTF-8 host string type (Python) * Limited access to GC internals hampers host subclassing (Go) * Mapping parcel/class names to host names and constructs (all) This is super fun stuff to work on. :) Having Lucy as a real-world example is invaluable during this period and I think releases will be coordinated for a while yet. Marvin Humphrey
