As you already know, plans for CEP2 are being dIscussed here.
which might extend to new content (under discussion in the thread linked above).
Regarding CEP3, I’m reluctant to go over very old ground, nor do I wish to be unnecessarily provocative, but since you insist…
Suffice it to say that many of us offered to help with CEP3, putting a lot of energy into articulating the issues, and offering to do the grunt work. Perhaps our help was not wanted, as the project went off in its own direction.
CEP3 seems to offer new content to start-up module builders only.
That left the community with 2 slightly different issues:
- No support for legacy modules using CEP2
- No clear direction for builders with modules-in-progress using CEP2 since they were not supported by CEP3
Potentially, CEP2 builders might take a chance on rebuilding their modules with CEP3 haks, but there are issues:
- Not clear that the new content is worth the rebuild and test effort
- Uncertain which CEP2 features have been taken out of CEP3
- No input to CEP3 project direction
- Not clear whether CEP3 will be supported or developed in future
At this point, Pstemarie took on support of CEP2, producing 2.67 to help those of us who are still building on that platform.
The new team took over when Pstemarie stood down.
Strategy is under discussion (see link above) but there are no plans for breaking compatibility with 1.69 or legacy CEP modules.
As for EE content, 2.67 already illustrates how it can be successfully included as an optional extra.
Going forward, the project has simply forked. As I see it, existing CEP2 builders will be served by the CEP2 team, while new builders can decide for themselves whether to go with CEP2 or CEP3.