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

Deprecate commons-redis #662

Open
wants to merge 4 commits into
base: master
Choose a base branch
from
Open

Deprecate commons-redis #662

wants to merge 4 commits into from

Conversation

ddworak
Copy link
Member

@ddworak ddworak commented Dec 24, 2024

Most of our internal products migrated or are in the process of migrating to Redisson so I propose to release a deprecation.

This module is particularly flaky and maintenance intensive so I've also removed it from CI.

@@ -33,7 +33,6 @@
[`OptRef`](http://avsystem.github.io/scala-commons/api/com/avsystem/commons/misc/OptRef.html) (implemented as value
classes)
* [Components](docs/Components.md) and Dependency Injection library
* `commons-redis` - [Scala driver for Redis](docs/RedisDriver.md)
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

suggestion: If we're keeping the Redis docs (I noticed you added deprecation notice in RedisDriver.md) until we remove the driver code entirely, IMO we should keep the entrypoint to its docs too.

@@ -45,6 +45,7 @@ import scala.concurrent.duration._
* @param config client configuration - [[ClusterConfig]]
* @param clusterStateObserver optional observer for monitoring client's state and connections - [[ClusterStateObserver]]
*/
@deprecated("Redis driver is scheduled for removal. Use a different library, e.g. redisson.", "2.21.0")
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

suggestion: Extend this deprecation notice (and other ones as well) with info that this is no longer tested since 2.21.0. If, for some maintenance reasons, we release new version in the future and someone encounters unexpected behavior, it might be a good clue for searching for the root cause.

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.

2 participants