-
Notifications
You must be signed in to change notification settings - Fork 57
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
Discontinuation of redis-7 for CentOS 9 #166
Comments
Hello, thank you for raising this issue. I am sorry that this issue caused so much problems to you. I will look into what happened and will try to fix the build and push action for the future. I have just pushed fresh images to quay.io so you should be able to use it now. We will support redis7 c9s image until the c9s itself is EOL. Please raise an issue again, if this does not hold (we will try to avoid that). About the communication of deprecation: we are aware that we could be better in it and are working on a systematic approach. Implementing ascii art is a good idea, we will think about it, thanks. Sorry again. |
The redis-7-c9s container is updated again. It looks like schedule rebuild disables also build-and-push action. Feel free to use it again. See https://quay.io/repository/sclorg/redis-7-c9s?tab=tags |
Closing as the immediate issue has been fixed. |
We've discovered1 two weeks ago that you've discontinued that redis-7 image for CentOS 9.
First of all, going through the quay.io repositories and having a reasonably obnoxious experience finding this repo (which is pretty much standard UX across Quay and Docker Hub), I understand that it's hard to propagate such decisions2 to the users, though I would very much appreciate if you tried to employ some way to deprecate images and warn potentially affected users (maybe warnings in the entrypoints of the images, even ASCII art to catch the eye; I definitely would've noticed that as I check on the deployment here-and-there).
My issue with this comes from the fact that I was not in any way aware of the discontinuation and “pulling the plug” on it. There are no commits, there are no issues, there are no warnings. I've found out about this decision at 5:30PM when the production died ( funnily enough, before the staging deployment :) ).
We already have plans to move on and since there are multiple alternatives, are you planning to maintain image of at least one of the forks, or we should look around for alternatives (possibly even non-CentOS based)?
Thanks.
Footnotes
sadly on our production deployment… ↩
like discontinuation of the maintenance because of the license changes ↩
The text was updated successfully, but these errors were encountered: