Closed (fixed)
Project:
Spam
Version:
6.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
5 Jan 2011 at 03:56 UTC
Updated:
24 Jun 2011 at 18:02 UTC
Thanks for all contributors to spam.module that recently fix *a lot of* pending bugs which keep this module much up-to-date and functioning.
BTW, may I request for a alpha/beta CVS tag for 6.x, e.g. 6.x-1.1-alpha? As we understand that the previous version of spam is now 6.x-1.0, which is quite buggy within latest LAMP. With a temporary alpha/beta release it may help newcomers to figure out which version would be more suitable for their daily usage, and also help web master for their daily maintenance.
Thank you very much.
Comments
Comment #1
gnassar commentedI think that's a great idea, and we're probably getting close to having a new beta ready to come out.
Comment #2
AlexisWilke commentedI'd like to know whether #1019902: "Mark as spam" links on comments give WSOD is a real alert... I'm testing now, so if I and others cannot reproduce it, I would suggest we get an alpha1 going. 8-)
Comment #3
AlexisWilke commentedI guess we're ready for a 1.1-alpha?
Comment #4
gnassar commentedWell, frankly I was going to jump straight to beta -- we've done a good deal of testing as it is.
We should probably give the Facebook Like WSOD problem just a little longer; I'm also hoping to have the last Action and some initial trigger code committed by the time we roll the beta.
Comment #5
AlexisWilke commentedActually, we probably want the #1006680: update_sql() does not take substitutions resolved first because people upgrading are otherwise going to lose their variables. I'll try to have a new patch sometime later today.
Thank you.
Alexis
Comment #6
gnassar commentedRight, that one was on my list too. Forgot to mention it.
I'd also love for #881570: Spam not working correctly with ajax comments to be fixed prior to that as well, but if testing shows that it does indeed break feedback functionality as I predict, it may be harder to fix than it seems.
edit: and the new one I just created too. :) #1022164: "Train as not spam" not implemented
Comment #7
john franklin commentedIMHO, #1006680: update_sql() does not take substitutions is certainly a release blocker, as changes to the db updates are hard to undo in later patches. If #1019902: "Mark as spam" links on comments give WSOD can be confirmed, it should be a critical bug and release blocker, too. But, #881570: Spam not working correctly with ajax comments can be fixed during the beta cycle or even in the next release and #1022164: "Train as not spam" not implemented can wait until 1.2.
I'm just saying this as a member of the community eager to get a new release and enjoy the amazing amount of work done on this module in the last few weeks.
Comment #8
AlexisWilke commentedJohn,
If you can test on a test server, #1006680: update_sql() does not take substitutions has a patch in #17 that would need testing and RBTC.
Be sure to either make a backup of your database or at least the spam tables before testing. The verify that your settings are the same before and after the upgrade.
Thank you.
Alexis
Comment #9
killes@www.drop.org commentedWe had to make a release due to a security issue. Bugfixing is still welcome.