From: marrco <as...@mi...> - 2008-08-10 09:01:09
|
>>Will do, but will 1.3.9.1 be ever published on sf ? When ? >> >>Or it's been aborted like 1.3.5 and next published version will be >>1.4.1.x ? > >Aborted? 1.3.5 has never been released to the public, so I call it aborted. Is 'skipped' a better name ? The fact is that now the last sf version is 1.3.3.10 and maybe 1.3.5 was better. > > Do you propose to publish 1.3.5 or 1.3.9 on SF, even when 1.4.1 is > already ready for primetime? Yes, definitely 1.3.9.1 No longer updated since a few weeks (assp.pl last updated June, 24, and last files in the .zip package were updated aug, 4th). I think 1.3.9.x has been long tested and has no known bugs, plus it has many new features above 1.3.3.10 And again, it's stable and tested for months. So my 2 cents are to publish 1.3.9.1 on sf asap. And now let's do a long test on 1.4.x in order to check for bugs, for minor glitches etc before releasing it to the public. I myself don't want to run on production servers your private versions, but only sf releases. And stability is really important to me. Sorry but 1.4.x less than 1 month ago had a major problem (attachment corruption) so I'm glad I decided not to use it. IT is my job, and there is no need to take un-necessary risks. I'm willing to wait one more month before deploying 1.4.x in a production environment, but I want a full tested release. Of course I will use 1.4.x on my test server, but nobody would kill me if a major problem stops mail flow on that mta. I think many new features have ot been really tested. Backscatter prevention. Can you tell me if it can stand a real backscatter problem, when a spammer forges a single email address, and you're getting 10k+ bounces per day on that single mailbox. Just blocking the undeliverable report and not the MS outlook read confirmation that come from the same ip space. And you can't allways use spf and outgoing mta is different than incoming. I bet many features have not been tested a lot, but we have 1.3.9.1 ready. Why not publish it ? Hope you get the point. I'm not trying to tell that 1.4.x and 2.x are not good versions, I just think that it's better to wait a few a bit longer before releasing to SF, and lately there have been too many buggy releases not ready for prime time. And that's not giving assp a good name. Assp deserves more users and popularity that it has now. Maybe a history of solid releases can help. So please, release 1.3.9.1 to sf and call the new 1.4.1 a 'release candidate' and everybody test it for the next few months before a new great, stable release. |