-
Notifications
You must be signed in to change notification settings - Fork 315
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
Add info about maintenance status. #2182
Comments
@ashthespy yeah, I totally agree. Would you help doing it? |
What is to be done with all the open issues? A lot of them are still valid.. |
Yeah but it will take days to get trough them, I would close them IMHO and just open the most urgent onese on volumio3 |
Are you sure? There are a lot of issues (and fixes/hints/ideas) here that would then be lost. |
I would prefer to keep them... but I don't have the time to go trough them, nor the support team.. |
Then it's a shame that we don't continue to use this repo! Especially considering most of the buster/v3 stuff was done already in this repo master...buster/master You could consider just renaming this repo to You also solve the issue of people searching for v2 support/code as
Personally, I am not a fan of issue management at $dayjob, let alone in my free time - so not going to be much help. I did close all my open issues though. |
Disable PRs/Issues and point people towards https://github.com/volumio/volumio3-backend?
The text was updated successfully, but these errors were encountered: