Is there a reason the official releases for 5.x and 4.7.x were withdrawn? They may be out of date but AFAIK they still work.

I ask because I'm still using 5.x-2.0 on a live site, and Update Status keeps complaining that my version of URLList is "Not Supported".

They don't have to be actively maintained, just the most recent stable "recommended" release...

Comments

deekayen’s picture

deekayen commented
Status: Active » Closed (works as designed)

http://deekayen.net/i-unmaintained-my-drupal-5-modules-purpose

kingandy’s picture

kingandy
he/him
commented

Hmm, well I see where you're coming from. I mean it's good to push people along with the Drupal upgrade wave. But just because you personally want everyone to use a more advanced version of Drupal does not mean that the existing version no longer works, or that it all of a sudden is full of bugs. It's still the "recommended release" for Drupal 5.0 and the project page should reflect that.

Do you really find it easier to come in and post that same link every time somebody asks about it? It seems like you're making yourself a lot of work, and giving people a lot of grief, just to make a point. Especially since the old modules are still actually available, and your "SFTU and upgrade" blog goes so far as to tell people how to not upgrade.

For what it's worth, I wasn't aware of the "(Don't) Warn if out of date" option on Update Status, so thanks for that.

kingandy’s picture

kingandy
he/him
commented

PS, have you considered posting that link on the project page? I'm sure it would save you some time.

deekayen’s picture

deekayen commented

I am only making a point as part of a larger personal time management issue. It's not fair to keep 5.x support checked off and give people the false illusion that if they file a 5.x bug, I'll do anything about it. I just don't have time to support all possible versions of the 50 or so modules I either maintain, co-maintain, or patch regularly, and all the other Drupal stuff I do.

kingandy’s picture

kingandy
he/him
commented

A note on the project page would achieve that goal without requiring feedback from yourself. Something to the effect of "5.x is no longer being developed or supported, please contact [xxx] if you are interested in maintaining the 5.x branch."