- Issue created by @benjifisher
- 🇺🇸United States benjifisher Boston area
Depending on where the documentation goes, we might want to move this issue to the queue for the
ecamodule. - 🇩🇪Germany jurgenhaas Gottmadingen
Not sure what we need to do here. The bpmn_io modeler is now already updated, and users don't have to do anything about it.
When it comes to an upgrade path from ECA 2 to ECA 3 (and bpmn_io going from 2 to 3 with it), that's being covered by ECA.
My guess is, we can mark this one as fixed, though?
- 🇩🇪Germany jurgenhaas Gottmadingen
I mark this as fixed, as the bpmn_io modeler 3.0.x is working, the ECA 2 to ECA 3 migration will be handled in ECA, and the only other modeler they may have to be upgraded is the Classic Modeler → for which I've opened the issue ✨ Add support for modeler API Active and will help the maintainers there to add support for it, when they're going to accept the idea.
The Camunda modeler → is being deprecated and won't be updated.
Other than that, there's no modeler around yet. And new ones should be developed for Modeler API right away and no longer the old way.
