-
Notifications
You must be signed in to change notification settings - Fork 551
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
Stop releasing broken software #3833
Comments
@Silex did you read the README.md statement? It’s super clear. Also, the team is busy upgrading Django, that’s the main goal, and made a lot of progress last months. Documentation is not yet updated and we make not guarantess. Again, read the README file. |
I see a lot of "further updates & modifications", which contradicts that statements and gives a false impression of activity/support. Your statement "the team is busy upgrading Django" also implies activity. But each release you do is broken as we cannot install the software. So I guess these releases are only useful to you. If only you tagged the latest stable release, maybe people could give the software a try. I tried the 20230926.1, it installs but then many things in the UI are broken. |
Again not what you are doing.
It's hard to participate when basic communication is missing. You'd add the following to the README:
|
Closing this. |
So, there's no old-but-stable version to use that you can mention? |
https://github.com/allegro/ralph/blob/ng/docker/ is outdated & broken.
https://ralph-ng.readthedocs.io/en/stable/installation/installation/ is outdated & broken.
Doing releases is meaningless if one cannot install your software.
@hipek8, @matyldv you guys should make a statement somewhere saying that the work you do on this repo is not meant to be used. Your activity gives a false sense of... activity, but it looks like the work you do here is only useful to Allegro internally.
The text was updated successfully, but these errors were encountered: