Am 27.08.2013 20:24, schrieb Paul J Stevens: > Hi all, > > I'm sorry to inform you that there is a rather serious problem with > 3.1.3 which can lead to corrupted messages in clients. > > Please do not upgrade to 3.1.x if you were planning to do so. > > If you have upgraded recently: the schema is compatible with 3.0.2 so it > is safe to downgrade. If that is not an option, keep your fingers > crossed. The problem only happens under severe pressure with many > concurrently connected users. I've been working very hard to track this > problem down, and fix it. As soon as I and my testers are happy, I'll > release 3.1.4 - which I expect to happen very soon: later this week
uhm - be carefull with "this week" since some of the problems are not reproduceable over many thousands of iterations for a lot of hours i would not consider a well tested version out this week - too much unkown variables this time even if we think after a lot of tests it is 100% clean and stable i go so far to not give a general OK after having a dediacted for release snapshot on production for at least one day from early-testers i fear i have to be one of them and so it would be cool if it goes well to prevent get killed by a user, my boss or by myself :-) i honestly dreamed from sunday to monday about patches and changelog descriptions solving some of the problems and had (not joking) http://git.dbmail.eu/paul/dbmail and specific patches in my dreams, woke up on monday, grabbed the smartphone from under the bed and was frustrated to realize it was only a dream, and yes i know how crazy and unhealthy this sounds... please no hurry this time :-) _______________________________________ only if i think back to the "POP3 no longer responds" where i needed 10 hours to get this damned debug triggered while debug-logging is on where it killed production server after one hour with a build that did work 23 hours before resulting a nervous phone call at 6:30 AM after consider the build stable at 5:00 AM and staring one hour on the logs i would say: give it time, doing fixes and *testing* with a lot of care and review any code which looks perfectly and could have been part of the problems one time too much is the way to go if i have learned one thing with 3.0 and 3.1 release then it is that there are way too much possibilities how a specific client trigger code paths and how this interacts with parallel load as well we need to keep in mind situations where the same user is accessing the same mailbox with a PC, Anroid-Phone and a iPad at the same time and even mix POP3/IMAP and all of this 3 clients may change the state with different commands and code paths well, the possibilities of unwanted interaction b etween the clients is large
signature.asc
Description: OpenPGP digital signature
_______________________________________________ DBmail mailing list [email protected] http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
