-
Notifications
You must be signed in to change notification settings - Fork 16
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
Automatically notify plugin authors about outdated plugins #73
Comments
We prefer the author to hand over the project to someone else instead of removing it completely. So the emails should:
|
SGTM |
@PerJensen had the idea that authors could manually mark a project as unmaintained. We should implement that first and then send notifications only about the projects not marked as such. |
It's possible also, for very simple plugins, that no changes are necessary. Eg. I have a couple of plugins from 1.8 beta that have not needed any updating all through 1.8 and I expect to work in 1.9. Should we have some way of marking them as still supported - that would prevent the 'unmaintained' message from showing for a while longer? Maybe a 'remind me in 6 months' or something? |
We could also just check whether the plugin compatibility has been updated. Simply tick the checkbox for 1.9 and you're done. |
good point |
Lets add a cron handler to notify plugin author if the plugin is outdated.
We could check e.g. whether:
The text was updated successfully, but these errors were encountered: