-
-
Notifications
You must be signed in to change notification settings - Fork 69
Deprecate this bundle #279
Comments
Even doctrine dropped there custom cache.
|
Let's start with the README #289 I don't have the right to edit the description and add [deprecated] like other packages |
@greg0ire @OskarStark can you do this? |
Done |
I'm wondering if it's not a bit premature… I mean we have lots of bundles relying on the cache bundle, shouldn't we move them to something else first? |
It's not like the package is abandoned or triggering deprecations though 🤔 |
IMO, we're just deprecating the package. Which means we're not recommending the usage of it, and recommend to use something else instead. When we're deprecating something in a bundle,
Adding |
And this sounds like step 3 |
I don't really know what is doing the dev-kit. And the "step 2" is still not finished for the core-bundle. So I can't say if we should revert these pr or not. |
I guess this must be in order to avoid extra work when a dev-kit PR does not apply cleanly to one of these bundles. I will merge the cache PR and deploy, this is probably fine 🤞 |
We should also add a new |
Wouldn't this trigger warnings for people using our other packages, like the block bundle? |
That's right but okay. We deprecated the bundle on GitHub, so we should deprecate the bundle everywhere |
This issue should be closed and instead one on PageBundle might be opened to track the efforts of remove this deprecated bundle from there. |
Feature Request
There is no need for the bundle anymore. Symfony / PSR cache is more common. Even doctrine dropped their custom cache.
The text was updated successfully, but these errors were encountered: