No. You shouldn't mix.
> Separately, does Hazelcast have a plan for supporting such
> compatibility going forward or announcing if it is broken? For
> example, I read that 2.0 will not be compatible with 1.9.4 in a
> mailing list post--however, I can't find official documentation
> referencing that (e.g. release notes).
2.0 and its documentation aren't complete. We should.. With 2.0 API is
changed. So your code might not even compile with 2.0. It is hard to
keep things compatible but starting with 2.0, we will try to make sure
that at least patch releases can run in the same cluster (2.0.1 and
2.0.2 for example).
-talip