-
Notifications
You must be signed in to change notification settings - Fork 71
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
Implement an action that lists forgerelease dates older than x #871
Comments
Hi! |
Regarding Rails: I dont know much about it yet, but I am willing to learn. I dont know if I could maintain and further develop voxpupuli tasks, since I am switching company and move away from puppet in that regard. Doesnt mean I wont be a part of voxpupuli anymore, I just dont have a clear view of how everything plays out ^^ But for the next 3-4 months at least I can pour some time into tasks and see where that leads :) Edit: Ok, just had a quick look at it and especially at https://voxpupu.li/. Big fan, will work on it :D |
I dont know if this is the right module for this.
In addition to the recent ci task printing a summary report of all modulesync versions that havent been patched into their corresponding modules yet, we could use a task that allows us to find stale modules / modules which havent had a release in a long time.
A cutoff point could possibly be something like last-released: 2 years ago.
If we have modules that havent had a release in that long time, we may have a stale module (candidate for archiving) or something else is broken/needs fixing (which would be good to know about). Thoughts on this?
The text was updated successfully, but these errors were encountered: