Hmm .. I think he will not hear it. :)
I don't have 1.9.9 build 14141. I have only build 14140 available
***** PLEASE could anyone send me a 1.9.9 build 14141 in a ZIP ! Thank
you ! *****
>(Very frustrating when you change a setting and it keeps
reverting on you!) - This one's been around for a long time.
Yes, for a very long time. This will have an end!
I've done some code corrections related to perlcritic S5 in 1.9.9 build
14154 - so I'll possibly do these corrections in 14141 again. I don't use
any V1 nor will I ever.
I'll change the build 14141 to 14156 and I'll make it available for
autoupdate on SF.
The corrected build will be 14157 and will be released as dev version on
SF-CVS.
Thomas
Von: "John Calvi" <webform...@lewis.com.au>
An: <assp-user@lists.sourceforge.net>
Datum: 21.05.2014 04:20
Betreff: [Assp-user] Resend mail regression in 1.9.9(14142)
There are increasing numbers of bugs in V1 from 14142 to 14154.
I saw a number of bugs in the code that I had identified earlier that were
then backed out from builds 14142 onwards and also new ones have been
introduced.
eg. Just a few examples are...
1. The block report you have mentioned here which I can verify was broken
@
version 14142,
2. The issue about nobayesian only working for outbound mails the fixes
for
which were backed out at version 14142.
3. This code added breaks the Bayesian scoring (due to $valence being
redefined) and is sloppy coding anyway as it does not take into account
different potential score settings (ie 49 assumes the default setting is
used) @ version 14154
if ($valence = 49 && !$this->{messagescore}) {
$valence = 51;
}
4. The default Bayesian cpu timeout config setting is 30s but in the code
if ($Config{BayesMaxProcessTime} > 15) {
$BayesMaxProcessTime = $Config{BayesMaxProcessTime} = 15;
}
Its limited to 15s. (Very frustrating when you change a setting and it
keeps
reverting on you!) - This one's been around for a long time.
I myself recommend staying at version 14141 until you are ready to update
to
V2.
These should have been Development versions and not rolled out for
production.
I think versions > 14142 should be flagged as dev and removed from the
auto-update system?
Perhaps 14142 should be copied to a 14155 version (fix item 4 above and
other known bugs) and made the current production release to get people on
autoupdate (or otherwise) off of version 14154?
John Calvi.
------------------------------------------------------------------------------
"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
Instantly run your Selenium tests across 300+ browser/OS combos.
Get unparalleled scalability from the best Selenium testing platform
available
Simple to use. Nothing to install. Get started now for free."
http://p.sf.net/sfu/SauceLabs
_______________________________________________
Assp-user mailing list
Assp-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/assp-user
DISCLAIMER:
*******************************************************
This email and any files transmitted with it may be confidential, legally
privileged and protected in law and are intended solely for the use of the
individual to whom it is addressed.
This email was multiple times scanned for viruses. There should be no
known virus in this email!
*******************************************************
------------------------------------------------------------------------------
"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
Instantly run your Selenium tests across 300+ browser/OS combos.
Get unparalleled scalability from the best Selenium testing platform available
Simple to use. Nothing to install. Get started now for free."
http://p.sf.net/sfu/SauceLabs
_______________________________________________
Assp-user mailing list
Assp-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/assp-user
