On 19/08/2014 02:55, Marvin Humphrey wrote:
Since Clownfish and Lucy will henceforth be separate products, I plan to run separate votes for this first independent release of Clownfish. In the future we might run a combined vote for the sake of convenience.
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.
On the other hand, it might be useful to test whether changes to Clownfish work with Lucy as soon as possible.
Reviewing the checklist at <http://wiki.apache.org/lucy/ReleasePrep>: * The RAT buildbot is currently passing for Lucy. We don't have a RAT buildbot for Clownfish AFAIK so I ran RAT locally and the output looked OK. * The issue tracker is clean for 0.4.0. * The Lucy CHANGES file has been brought up to date and the Clownfish CHANGES file has been inaugurated. * LICENSE and NOTICE look correct for both Lucy and Clownfish. * As of a week or two ago, Lucy and Clownfish built and passed tests on a variety of Windows configurations, plus Linux, FreeBSD (our buildbot) and OS X. It might be nice to check NetBSD and Solaris. * The valgrind test targets have been modernized to use a more flexible suppressions format and are now more reliable and less fussy about compilation options and Perl versions. I'll give it another pass before submitting the RC but they should be passing. In addition, the update_version scripts have been been adapted for the changes since 0.3.x and I've checked the product of the CPAN dist building process. Every module listed in 'provides' has the correct version number (though to be honest the list of classes is not exhaustive) so we should get a clean index on CPAN.
Looks good. Nick
