This must be a bug that folks have filed previously. Heck, I think I've filed one previously, but I wasn't able to find it.
When modules like http://drupal.org/project/content_multigroup get removed from support they shouldn't be nixed like they were never there.
There should be some page that explains why they were removed, perhaps ways that some of the functionality can be replaced, but most importantly what to do now that you've got a module that's likely insecure on your live site.
Sure, you can just delete the code as suggested in admin/reports/updates and pretend it was never there, but that's not likely going to fly with folks who are using the site.
I don't know how to change the process. Perhaps it would be possible to sign up for alerts on specific modules. Heck, I'd have no concerns letting Drupal know a contact email they could use when there are problems with a given module that need immediate action.
Is there already a bigger thread on how we should deal with this? If so where? Can we direct deleted projects to a page with a link there?
Comments
Comment #1
gregglesIn general project pages should only be deleted if there is no code associated with them.
In every other case they should be kept and an explanation added to them. Deleting this was a mistake. We should probably recreate it.
Comment #2
mgiffordThanks!
Comment #3
tvn commentedClosing old issues. Please re-open if needed.