Hi everyone,
I’d like to invite you to discuss a new proposal for Operaton: introducing Preview Features.
Operaton evolves quickly and benefits from early feedback on new functionality. At the same time, committing too early to long-term compatibility guarantees—especially around BPMN/DMN semantics and persistence—can create risks and long-term maintenance overhead. The proposal aims to balance these concerns by introducing Preview Features inspired by Java’s JEP 12 model.
Preview Features would be explicitly opt-in (disabled by default), time-boxed, and not covered by compatibility guarantees. This allows us to integrate and validate new functionality earlier while keeping expectations clear and avoiding accidental lock-in of unstable behavior.
I’m particularly interested in your thoughts on whether this approach strikes the right balance between fast delivery and stability, and if there are any risks or improvements you see.
GitHub PR: https://github.com/operaton/operaton/pull/2404
Feel free to comment directly on the PR.
Looking forward to your input!
Tobias