.....
And facts are: almost every new feature added to eMu caused sync proplems in previous betas. And we heard the same claims that "new version will fix it", "the tests in closed circle went good", but new problems arize again and again.

.....
Why do on earth you ever began to talk about me? What i have to do, what not, am i greedy, have i a boat, what i should say?

*sigh*
Ok lets look at this....
Many many many months ago, transactions had sync problems...because well, transactions were still being refined. After a number of betas, transaction sync issues were no more.
Then a new feature was added, ENS. ENS has its own sync channel but is referenced by the transactions model (to ensure you paid for the ENS). ENS is new code, so it is going to have problems....some of which were syncing. Syncing problems in the new ENS code on occasion caused issues in the transaction syncing...eventually they were all fixed.
But (and this is important Starik, so read it twice!)
sync problems in new ENS code are NOT sync problems in transaction code. If you think that its possible that any new code does not have bugs, well, you must live on Mars. Furthermore decentralized systems spend a lot of time in synchronization with the network. The more features you have, the more syncing channels you need, and the more possible bugs.
Also, isn't testing for these problems what Beta Testing is about??? If there were no bugs, syncing or otherwise, it wouldn't be called Beta, it would be called V1.0
-----
Alas, I don't know why I am even bothering to reply to you, every single post anywhere regarding pretty much anything (not just eMunie), you are negative and attempt to twist things to stir up FUD. I do not ever recall a single positive or even constructive comment about eMunie...you just bash. I don't need bashers that offer no solutions and that is why I tend to ignore you.
Not sure why you mention about having boats.....Mars has no water.