On 14/11/06, Carl Trieloff <[EMAIL PROTECTED]> wrote:
To this end my a propose a third option:
- branch to release what we have now (This is a good so that we can
work through all the apache release procedures)
- when we release C++ and other components in a few weeks time (maybe
push back to Dec) we call it M2 and re-cut an update of Java
- with maven + new code generators, persistence etc....
This works for me. I was going to propose (after M1 was out of the
way) that M2 was scoped to be maven, persistence and as many JMS
compliance improvements as we could achieve. That would push the major
HA and protocol changes into an M3 in January.
I was hoping that we could get that M2 out in December (although
realistically I had thought mid-December). The motivation for that is
that we have a major project that does not require HA but does need
the persistence changes and I imagine their needs are not unique.
RG
