semver broken in 1.2.0, 1.2.1, 1.3.0; transitive dependancies

[nevans]

Starting with 1.2.0, redis-namespace depends on redis ~> 3.0.0, but before that it depended on redis < 3.0.0. redis 3.0.0 is chock full of tiny annoying (albeit good and overdue) backwards incompatible changes, but apps that use redis heavily will need to deal with all of those changes before they can upgrade to redis 3.0.0.

But this means that upgrading from redis-namespace 1.1.0 to redis-namespace 1.2.0 or later is also backwards incompatible (for the apps that use the changed features). Likewise, other gems that depend on semver to protect them from backwards incompatible changes in redis-namespace (e.g. resque) will also get taken along for the ride.

blech!

[yaauie]

I'd vote for maintaining a redis-namespace-1.1.x series for redis gem ~> 2.2 and backporting some of the fixes that have gone into it. It's less than ideal from a semver perspective, but we can't exactly un-release.

I would be willing to take on the role of maintaining the branch if you need someone to fill the role.

[yaauie]

It's been long enough since this has happened that I'm going to just have to close it. Even though I'm maintaining the gem moving forward, there is enough of a divergence that I don't think it's worth backporting anymore.

😦 semver is hard