- Issue created by @jurgenhaas
- 🇩🇪Germany jurgenhaas Gottmadingen
I suggest creating a 2.0.x branch of eca_cm, and I would provide the necessary changes as an MR then. OK?
- 🇩🇪Germany mxh Offenburg
This makes sense to be addressed once ECA v2 reaches beta, as beta releases are usually not supposed to make major API changes anymore.
- Status changed to Postponed
11 months ago 9:46am 5 August 2023 - Assigned to jurgenhaas
- Issue was unassigned.
- Status changed to Closed: outdated
about 1 month ago 3:33pm 24 May 2024 - 🇩🇪Germany jurgenhaas Gottmadingen
I've reviewed the current 1.0.x-dev branch and there is nothing that needs adjustment for ECA 2, therefore I'm closing this issue.
@mxh if you want to continue maintenance of this modeller, the constraint for ECA may be opened up to allow any ECA version, and then it probably also needs some attention for the Drupal 11 release, which is due in July.
- 🇩🇪Germany mxh Offenburg
@mxh if you want to continue maintenance of this modeller, the constraint for ECA may be opened up to allow any ECA version, and then it probably also needs some attention for the Drupal 11 release, which is due in July.
Yep, thanks for the note. Definitely it will require at least an update regards supported versions, and possibly some adjustments for being compatible with D11. I'll take care of that when possible.
