My "available updates" section on my Drupal site lists that the Spam Module should be updated to 5.x-3.0-alpha5 -- the Spam module front page says that 5.x-3.0-alpha5 is the "recommended version" for 5.x installations of Drupal -- it is, in fact, listed as an official release.

However, the README.txt file in the module itself says this:

As of Alpha1, the module is now minimally capable of filtering comments. It has a long ways to go before I'd recommend actually using it in production, but testers and contributors are always welcome.

... if this is the case, why is it being pushed as the official release? By the filename's own description it is still an alpha release, but on the Spam page it is listed as the "recommended release!"

I've tried using it and I've run into some problems -- which I intend to file bug reports for -- but it seems awfully premature to be pushing this as the latest release!

Comments

jeremy’s picture

jeremy commented
Status: Active » Fixed

"However, the README.txt file in the module itself says this:"

The README file should be updated. The module is much more stable and functional than it was in alpha1. The big missing piece yet to be coded is support for reporting mis-filtered content.

"... if this is the case, why is it being pushed as the official release? By the filename's own description it is still an alpha release, but on the Spam page it is listed as the "recommended release!'"

I have a very finite amount of time to put into maintaining this module. I don't have enough time to maintain anything but what I'm using myself. I'm using the 3.x version of the module, so that's become the official and recommended version. I don't want to list the old version as the official and recommended version, as I'm no longer supporting it.

"I've tried using it and I've run into some problems -- which I intend to file bug reports for -- but it seems awfully premature to be pushing this as the latest release!"

I consider it premature to complain about this version of the module being unusable if you've not even contributed back bug reports... ;)

Yeah, I agree this is not an optimal situation. I wish I had time to finish the module and roll out an official release. I estimate there's only about 40 hours of work left to polish of the module and roll out an official 3.x release. Once that's done, the next step is to port it to 6.x. Eventually I will find the time.

ubersoft’s picture

ubersoft commented

I consider it premature to complain about this version of the module being unusable if you've not even contributed back bug reports... ;)

:D

For the record, I didn't say it was "unusable" -- I said there were problems. But I was alarmed that the alpha was being listed as the official when the readme file said it wasn't ready for it. I'm sure you can see how it would be reasonable to conclude that the problems I encountered were indicative of greater problems when the package describes itself as not ready for release. The only information I have is the information I get here and in the plugin itself...

jeremy’s picture

jeremy commented

Understood. The ";)" was there to indicate that I wasn't being serious. As I noted, things are suboptimal with the spam module for now, but hopefully I'll find the time to clean things up to a releasable state soon, including updating the documentation.

Anonymous’s picture

Anonymous (not verified) commented
Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.