- Issue created by @jurgenhaas
- Merge request !2Issue #3379343: Version 2.0.x for ECA compatibility → (Merged) created by jurgenhaas
- Status changed to Needs review
over 1 year ago 3:58pm 4 August 2023 - 🇩🇪Germany jurgenhaas Gottmadingen
This should probably go into a new branch 2.0.x
- Status changed to Postponed
over 1 year ago 9:45am 5 August 2023 - 🇩🇪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.
- Assigned to jurgenhaas
- Status changed to Active
7 months ago 12:00pm 24 May 2024 -
jurgenhaas →
committed 279a0a0b on 2.0.x
Issue #3379343 by jurgenhaas, mxh: Establish ECA 2.0 compatibility
-
jurgenhaas →
committed 279a0a0b on 2.0.x
- Status changed to Fixed
7 months ago 1:02pm 24 May 2024 - 🇩🇪Germany jurgenhaas Gottmadingen
I've completed this issue and merged it into 2.0.x-dev so that testing and improvements can be made there with individual issues, if necessary.
-
jurgenhaas →
committed a9c5b4db on 2.0.x
Issue #3379343 by jurgenhaas, mxh: Establish ECA 2.0 compatibility
-
jurgenhaas →
committed a9c5b4db on 2.0.x
-
jurgenhaas →
committed 0ad965af on 2.0.x
Issue #3379343 by jurgenhaas, mxh: Establish ECA 2.0 compatibility
-
jurgenhaas →
committed 0ad965af on 2.0.x
Automatically closed - issue fixed for 2 weeks with no activity.
