On 10/26/2006 4:48:39 PM, Gerhard Killesreiter (gerhard@killesreiter.de) wrote:
In most cases the reason probably is "maintainer forgot to set it". Feel free to change it to the latest release, it can easily be changed back.
Ok, will do.
It is always difficult to guess wether a module is truly abondoned. I myself have modules that don't yet have a 4.7 release since I don't use them myself and there aren't enough patches.
But if for example the latest commit is like one year ago on the 4.6 branch and nothing on HEAD since then, it is safe to assume it won't be updated any time soon and maybe never. Adding a note about this will save people from wasting their time with it. Feel free to add such notes, they can also easily be removed. Add something like "this module hasn't been updated in a long time and the author isn't very resresponsive. It is possible the module is abondoned. The management."
That will take a little investigating in each one, so I'll go back through and do that once I've gotten the rest taken care of. Thanks. Michelle