Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Replace laminas-cache with psr/simple-cache #146

Open
wants to merge 1 commit into
base: 2.30.x
Choose a base branch
from

Conversation

marcelthole
Copy link

Q A
Documentation no
Bugfix no
BC Break yes
New Feature no
RFC yes

Description

laminas-cache supports PSR-6 and PSR-16 and there is no reason to depend on that laminas-cache anymore. This should also reduce the overall dependencies for updating for new PHP versions or the laminas servicemanager migration.

Question: is it fine to use only the psr-16 implementation?

Additional Notes

I didn't found a Issue for the Todos for a new 3.0 Version for laminas-i18n. I guess there are also some other improvementes for that version like updating the servicemanager to version 4.1 and use native property types

@froschdesign
Copy link
Member

@marcelthole
Please see also: #120

laminas-cache supports PSR-6 and PSR-16 and there is no reason to depend on that laminas-cache anymore.

Correct!

Question: is it fine to use only the psr-16 implementation?

Sure!

I didn't found a Issue for the Todos for a new 3.0 Version for laminas-i18n.

An issue report should not be the first choice for this, milestones and projects should be.

@marcelthole
Copy link
Author

Please see also: #120

Oh looked only in the issues and not in the open PRs :/

An issue report should not be the first choice for this, milestones and projects should be.
is there an idea already to create the project?
Would be great if i could update to PHP 8.4 in one of my projects but there are still some packages that doesn't support the servicemanager v4. A roadmap would help me here a lot to create the correct PRs

@gsteel
Copy link
Member

gsteel commented Jan 9, 2025

Side note @marcelthole:

Validator 3 is done, Filter v3 is nearly there. Once filter v3 is out, the next item is probably input filter major release, then form and then view.

Because i18n may require a major release to support any/all of the above, we should avoid releasing a major here until we are sure that upgrading deps doesn't force a major release, i.e. it would be bad to release v3 here prior to view v3 only to find we've got to release a v4 for comapt with view (for example)

@froschdesign
Copy link
Member

@marcelthole @gsteel
I will create a project and add the next steps/components to show the current planned upgrade path.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants