Open Koen1999 opened 1 year ago
Great to see they are making progress on this, before we start testing this we should fully implement the changes required by GEWIS/gewisphp-coding-standards (I have already started on this, this is already fully implemented in GEWISDB). This will allow us to write better code and easily allow us to determine whether something is our fault or something is broken upstream.
https://docs.laminas.dev/laminas-servicemanager-migration/ already has some migration details, the FactoryInterface
for Psr
is going to be interesting, because we currently utilise it to handle the ACL:
v4.0 is out, see https://github.com/laminas/laminas-servicemanager/releases/tag/4.0.0. It will take some time before all components are compatible (or are marked as abandoned because that is the general direction Laminas MVC seems to be going).
Based on the TSC meetings over the past 9-ish months, it is very likely we will never be able to upgrade to version 4.0 (or later) of the service manager due to decreasing contributions to the whole of Laminas. The current bottleneck is laminas-mvc
(and thus the whole framework) with many of its dependencies (components) not receiving updates.
Based on the TSC meetings over the past 9-ish months, it is very likely we will never be able to upgrade to version 4.0 (or later) of the service manager due to decreasing contributions to the whole of Laminas. The current bottleneck is
laminas-mvc
(and thus the whole framework) with many of its dependencies (components) not receiving updates.
Bit sad it might die like that. It's not a bad framework, but I guess it suffers from competition. As long as we receive security updates we should be okay though. I don't think there's any functionality we are really missing at the moment.
What would you like?
Please see https://github.com/laminas/laminas-servicemanager/releases/tag/4.0.0-rc1
Why is this needed?
Early testing might help fix bugs upstream.
Other information
No response